WRT310N Connection is horrible when using WPA

I bought this router Nov 3rd of 2008 and it worked fine for a few days then I setup WPA and the connection starting dropping. I can't hold a connection on any of my wireless devices, however if I just let the router sit with the factory settings I have no issues with connectivity.
Any ideas?
P.S.
I upgraded fireware first day I got the router.
-Cameron
Solved!
Go to Solution.

Change the MTU settings on the router.
Login to http://192.168.1.1, leave the username and password - admin
Change MTU - manual and size to 1350 and save the settings.

Similar Messages

Do I have to be connected to internet when using illustrator through creative cloud? And can I change the language on the trial version if I would extend it to pay version? Thank you in advance.

Do I have to be connected to internet when using illustrator through creative cloud? And can I change the language on the trial version if I would extend it to pay version? Thank you in advance.

Lelisa it is only necessary to connect to the internet periodically to receive updates and validate your membership. If you have an annual membership you can be offline for up to 99 days. You can find additional details at Activation & Deactivation Help.
I would also recommend reviewing Creative Cloud Help | Install, update, or uninstall apps which discusses adjusting the installation language.

New iPad won't connect to Mobile Hotspot using WPA or WPA2

I have a new iPad running iOS 6.01. It connects to wifi networks perfectly. I also own a Blackberry 9790 that is capable of running a wifi hotspot. When I try to connect my iPad to the mobile hotspot when WPA or WPA2 Encryption is used the iPad cannot connect. If I change the Encrypstion to WEP I am able to connect the iPad and wifi works on it.
Is there a reason the new iPad won't connect to a mobile hotspot that's using WPA/WPA2? Is there a way to resolve this issue?
I am able to connect my MacBook Pro to the mobile hotspot using WPA/WPA2 so I know that it's not my phone or the hotspot not working properly.
Thanks

It appears as though I fixed my own problem...I hadn't yet tried restarting my blackberry or my iPad since I had been trying to setup the mobile hotspot and connect the iPad. Anyways, I restarted both devices and then tried connecting using WPA/WPA2 and it worked.
iPad is now connecting to my mobile hotspot using WPA/WPA2 with no problems.
Maybe try doing the same if you haven't.

JDBC connection pool failures when used by JMS stores

          We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
          a JMS Store.
          <JDBCConnectionPool Name="sybaseJMSPool"
          Targets="cluster00"
          InitialCapacity="2"
          MaxCapacity="10"
          DriverName="com.sybase.jdbc2.jdbc.SybDriver"
          Properties="[email protected]@;[email protected]@;charset=utf8"
          URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
          (note that the @xxx@ string are replaced by actual values).
          We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
          We deployed this configuration on a number of environments (testing, staging,
          ..). The actual hardware and network configuration is different for the different
          system, but the WebLogic domain stays the same regarding this issue.
          On the test system we frequently get the following exceptions:
          <Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
          <ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
          <JMSServer "JMSServer00", store failure while writing message for topic
          OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
          <sybaseJMSPool>, prefix = <JMS00>: write failed
          java.sql.SQLException: JZ006: Caught IOException:
          com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
          closed.
          at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
          (ErrorMessage.java:715)
          at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
          at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
          at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
          at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
          (SybStatement.java:1625)
          at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
          (SybPreparedStatement.java:91)
          at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
          (P6LogPreparedStatement.java:179)
          at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
          at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
          at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
          at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          .>
          java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
          = <JMS00>: write failed
          java.sql.SQLException: JZ006: Caught IOException:
          com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
          closed.
          at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
          (ErrorMessage.java:715)
          at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
          at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
          at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
          at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
          (SybStatement.java:1625)
          at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
          (SybPreparedStatement.java:91)
          at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
          (P6LogPreparedStatement.java:179)
          at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
          at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
          at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
          at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          at weblogic.jms.store.JDBCIOStream.throwIOException
          (JDBCIOStream.java:1213)
          at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
          at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
          at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Before that this message appeared:
          <Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
          <node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
          <Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
          received a message over an uninitialized connection: 'JVMMessage from: 'null'
          to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
          1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
          invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
          offset: '34'''>
          This problem did not occur on another system which was used during a 2 day stress
          testing session.
          It seems that the problem occurs after a period in which no user request where
          made. The user requests trigger EJB's that start sending JMS messages.
          When the problem occurs, the JMS messaging systems seems to lock up as no messages
          are received anymore by the different listeners (MDBs).
          Undeploying and redeploying the JBDC connection pool solves the problem. This
          solution is unacceptable in case of a production system.
          A similarly defined connection pool, which is used by the EJBs to make database
          connection, does not manifest this problem.
          <JDBCConnectionPool Name="sybasePool"
          Targets="cluster00"
          InitialCapacity="10"
          CapacityIncrement="5"
          MaxCapacity="50"
          PreparedStatementCacheSize="150"
          DriverName="com.sybase.jdbc2.jdbc.SybDriver"
          Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
          URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
          The JDBC connection pool is used as follows by the JDBC store
          <JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
          <JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
          <JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
          <JMSTopic JNDIName="ADIS.Status"
          Name="StatusTopic" RedeliveryDelayOverride="300000"/>
          <JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
          Name="OrderChangeTopic" RedeliveryLimit="3"/>
          </JMSServer>
          Turning on the "Test Reserved Connection" with a appropriate test table does not
          help.
          Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
          can be related to network problems. Nevertheless the connection pool should be
          able to cope with this.
          Can you provide any solution for this ? Or give us hints what can cause the problem


Zhenhao Qi wrote:
thanks! Joe.
The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
allowances for one thread to interrupt a second thread's JDBC call. If we
transmit your timeout request by calling setQueryTimeout() on the oracle
statement, and if you have a weblogic-controlled transaction we call
Statement.cancel() on any ongoing statement, we end up relying on whether
the Oracle driver implements and responds to those calls.
Are you doing weblogic-controlled transactions? Are you/can you
call Statement.setQueryTimeout() on your statements, or are these
generated JDBC queries?
If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
we have some other debug avenues. This would be good even if you really
want to use the thin driver, because we will do the same JDBC calls to
either driver, and the debug would prove (if) we set up a query timeout
and if we call cancel(). If we do, then we can know that it is the Oracle
driver failing in these regards.
Joe

Leopard problem connecting with wifi AP using WPA PSK instead of WEP

I cannot connect via Airport to Speedtouch 580i accesspoint using WPA PSK.
WEP works just fine, but using WPA PSK I keep getting the message invalid password and then cannot connect wirelessly.
Tiger as of version 10.4.3 through .11 worked flawlessly via WPA PSK with the same AP.
I installed 10.5.4 Leopard from scratch and used combo 10.5.5 and and a few days ago combo update 10.5.6 but problem remain.
After the clean install I used migration assistent to get user data and logins from Tiger into Leopard, having used an image made with SuperDuper.
I have read many support forums and suggestions, it all didn't result in a working internet connection at all with WPA PSK :-...(
What I did until now:
- Disabled IPv6 for the airport interface
- Changed to a simple WPA PSK password without CAPITALS instead of something like #A!$($D$%\T@q{|
- Changed to a fixed channel in the wireless accesspoint instead of auto. http://discussions.apple.com/thread.jspa?threadID=1195706
- Rebooted Accesspoint various times.
- Changed to 802.11g only instead of b+g
- Tried both TKIP and AES as encryption type
- Disabled and re-enabled Firewall in Leopard
- Changed to fixed ip adress instead of via DHCP for network addres assignment
- Tried connecting with and without broadcast of SSID to AP.
- Repaired keychain , http://discussions.apple.com/thread.jspa?messageID=5858982
- Did various keychain changes incl deleting old values
- Deleted some items from library, as per suggestions from forums.
In the end I have a suspicion that it all drills down to something simple, quotes (" ") are used to present the password in the password field, at least this is the case with WEP, but this does not harm the functionality for WEP as this is working alright.
With the current WPA PSK implementation it perhaps does influence, because it keeps saying invalid password. I have tested both with and without quotes and things did not improve at all.
I'm running out of ideas to solve this matter, therefore I have sent a report to Apple via their Feedback webpage.
While having using 10.5.5 fo a while I had big hopes 10.5.6 would cure the problem , unfortunately this is not the case.
Please provide more suggestions to solve this problem.

Checked Accesspoint firmware upgrade. The only difference between the current 4.2.7.25 and the latest version, 4.2.7.30 is the support of WDS i.e. expanding the wireless network by connecting 2 APs together (via WEP).
Still tried upgrading via the MAC OS X update software, it did not fire up, I think the software is not fond of Leopards
As WEP works ok with Leopard on my G4 Powerbook 12inch, I didn't want to focus further on the speedtouch because of the motto 'if it ain't broke don't fix it.'
Am going to research more on Keychain and DHCP, others are reporting issues with it along with this 'airport crisis' http://forums.macrumors.com/showthread.php?t=375838

Internet disconnecting when using WPA

About 3 weeks ago my wireless connection started dropping on a regular basis. I would be on the web, and then i would not be able to access any pages. Everytime, I would have to power cycle the router and the wireless would reconnect....then about an hour later, same issue.
I contacted Verizon tech suppot and he could not connect to my router because I was using WPA for security instead of the default WEP. The tech told me that Verizon was trying to push out some updates or something and that they could not because I was not using THEIR recommended security settings of 64 bit WEP.....he said I would have to revert to WEP or I would continue to have problems.
I reverted back to WEP and have had no problems at all. Everytime I try to put WPA back, I have the same issue.
Anyone else having this issue?
Personally, if this is true, I'm not going to be very happy about this. So either the tech was an idiot or Verizon is being **bleep** by not allowing people to use a different security setting.

thats what i was thinking too. I'll have to check the setup for WPA, I have the Westell 9100 router, so I'm not sure it has the same setup as the ActionTec.
Thanks for the info. I'll check tonight/tomorrow and post my findings.

Cannot connect to mobile hotspot using wpa; only open security works

I have a Galaxy S5 and am trying to connect to the mobile hotspot using my Surface tablet. If I have the mobile hotspot setup using WPA2 security with a password I cannot connect however I can connect if I am using Open security.
I can connect the surface to other routers using WPA security, just not the Samsung as a mobile hotspot.
does anyone have any suggestions?

What you have proved here is that your tablet has a password conflict somewhere. You should find out where your wireless profiles are being stored on that device, wipe them out and then try connecting again. Once you provide the tablet with all of the correct connection credentials and configurations it should connect just fine.
Connecting without a password proves there is not a WiFi issue. Connecting to other devices is additional proof that there is not a WiFi issue going on. You just need to straighten out the security issue and then will be good to go.

Wget - Connection timed out when using "long" strings

I'm having a problem with a little script to change some settings for IP-phones. Here is the script:
#!/bin/bash
for i in "0" #"4"
do
for j in $(seq 176 176)
do
wget --timeout=1 --tries=1 --keep-session-cookies --save-cookies cookies.txt --post-file=postfile http://192.168.$i.$j/dologin.htm
wget --timeout=1 --tries=1 --load-cookies cookies.txt --post-file=postfile2 http://192.168.$i.$j/update.htm
done
done
postfile looks like this and is just for logging in:
P2=<pass>&
postfile2 looks like this:
P270=123456&
The problem now is, when using it like above, everything works fine. But if I make the text in postfile2 one character longer, I get this:
Connecting to 192.168.0.176:80... connected.
HTTP request sent, awaiting response... Read error (Connection timed out) in headers.
Giving up.
It doesn't matter where I put the character to make the string longer (I can for example use P32=1234567& and it works). I have tested the script from different machines and used different phones, always the same. Any ideas?

daf666 wrote:The two files look identical, are you sure that the "bad" one is actually a capture of the timed out session? (both have same data length and same value in the content-length header).
Yes, they are different and the bad is is from the timeout .
daf666 wrote:Anyway, this timeout might occur, if for some reason wget will say content length is 10 and send only 9 characters in the post request..
Any idea what I can do about it? There is something fishy going on. I did this once before a few month ago when I wanted to change other settings. I tried to do the same thing again but even this doesn't work anymore. Maybe I should just try curl .

Firefox throws "This Connection is Untrusted" when using hostname, but not when using IP address

I am remotely accessing a website which has iFrame in it. The website uses https, but iFrame tag has "src" pointing to a site using http only. However, when I remotely go to the site, iFrame shows the message below although the ''src" url is http only (there is no SSL certificate) when I use IP address (https://10.10.101.156:8006/apprecovery/admin/Core/Storage) in address bar instead of hostname (https://hostname:8006/apprecovery/admin):
===
This Connection is Untrusted
You have asked Firefox to connect
securely to d37t50w1, but we can't confirm that your connection is secure.
Normally, when you try to connect securely,
sites will present trusted identification to prove that you are
going to the right place. However, this site's identity can't be verified.
What Should I Do?
If you usually connect to
this site without problems, this error could mean that someone is
trying to impersonate the site, and you shouldn't continue.
d37t50w1 uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
(Error code: sec_error_ca_cert_invalid)
===
Why is it giving this when using hostname but not when IP address is using?

Corrected first para above:
I am remotely accessing a website which has iFrame in it. The website uses https, but iFrame tag has "src" pointing to a site using http only. However, when I remotely go to the site, iFrame shows the message below although the "src" url is http only (there is no SSL certificate) when I use hostname address (https://<hostname>:8006/apprecovery/admin) in address bar. But I dont see the message in iFrame when I instead use IP Address (https://<IP Address>:8006/apprecovery/admin) to go to main website.

Basic Airport card can't connect to Wi-Fi using WPA encryption

I have a Powerbook Pismo 500mhz using OS 9.2.2 and Airport 2.0.4 software with a basic Airport card installed in it. For over a month I was able to connect to my resorts wi-fi network by putting in there Key 1 password and I was connected just fine. The other day they changed the password and upgraded there software from WEP to WPA, Now no matter what I do I can't get it to accept my password. The password is 24 letters long and every time I enter it I get "An error occurred while trying to join the selected airport network" .
I have tried everything from putting the password in quotes, to starting it with $, to even using Wep Key maker. In fact they call it a PassPhrase, not a Password. There is no options to change the encryption with Airport 2.0.4. I have looked all over the net and this is my last resort. Please help. If you wish you can email me directly at [email protected]
Powerbook Pismo 500 Mac OS 9.2.x Basic Airport card, 768 ram, 30 GB HD

I've been having horribly similar problems trying to get my Mac to join up with a non-Apple Wi-Fi network running WPA.
I suspect you are probably entering the WPA password into the old WEP password field on your Powerbook. If you are, that will never work. You need to have the system asking you for a WPA password not a WEP one, and if you're software isn't current you won't be given the option.
Try this - you need to get your OS level and airport drivers much more current. I was experiencing the same error message as you when I was on OSX 10.3, which I have a feeling is the first level of OSX that properly supports WPA. Move up to 10.4 if you can. Also get the latest Airport drivers installed. Henry B may be able to give you the link, or you will find it embedded in another post.
If you are as unlucky as me you may find that even this doesn't fix your problem. I'm now getting the message that my password is not accepted - a step forward but not a cure.
If you do manage to get it going (and all advice is that the OSX upgrade and new drivers usually do the trick), let me know what your fix was!
By the way, things also seem to work better if you have your SSID broadcast by the Access Point.
Richard

Connecting MBA to domain using WPA Enterprise

Hi guys!
I'm having "the usual" new MBA WiFi-problems, meaning my MBA keeps dropping the WiFi connection occasionally, but that's going on in another thread.
I don't know whether this is a related problem, but I can't seem to connect the MBA to the WiFi network at the office at all. The network connection dialog tells me my connection needs WPA Enterprise credentials, but no matter what I write, I won't get connected.
So I'll start with the basics. This works for every other device I have (PC laptop, iPhone, iPads and so on):
Username: \\MyDomain\MyUserName
Password: MyPassword
But not for the MBA. For the domain/username, I've tried single \´s and /´s and just about any combination just in case this is a "Mac syntax thing" (this is my first Mac laptop), with and without the MyDomain part, lowercase, uppercase, quotation marks around the password (as I saw mentioned in some thread in the case of alphanumeric WEP, or some such), but nothing works. I don't remember the exact error message, but it has to do with the authentication server perhaps not being available.
Apparently others have had problems with the WPA Enterprise connections as well, but could somebody just confirm that the \\MyDomain\MyUsename -syntax I'm using is indeed correct.
Cheers,
Kim

Marc,
I'm suprised that WPA works over WDS. I had thought that because WPA cycles the encryption key with each message transmission that the two Airport devices would quickly get out of sync.
But I do respect Alan's opinion, so I'd give in to his statement that it does work, I'll be searching through the update readme's to see when it started working.
You could always drop back to WEP encryption. Unless you have the FBI next door listening in and analysing all your network traffic, it's not going to be broken.
WPA changes the encryption key with each wireless message, WEP doesn't. So in theory, with WEP, someone could analyse all your network traffic, looking for patterns. You can work out just how hard that is.
If you choose an obvious password (like from a dictionary) it won't matter if you're on WPA instead of WEP, the Feds / hackers will be in in a short time.

Lose connection to E1000 when using Windows Live Messenger

I have a laptop running Vista which connects to the Internet through my Linksys E1000 wireless router. We have installed Windows Live Messenger, v2011 on the laptop, but whenever we try to login, the E1000 appears to crash. It is still running, but we cannot get an Internet connection on any computer in the house. I must then reboot the E1000 and the DSL modem in order to restore the Internet connection. I spoke with Linksys technical support for over an hour, and tried different things, but the E1000 continues to crash when Windows Live Messenger is used. The technical support person suggested that I may need to investigate "port forwarding" for WLM. Could this be the problem? And if I find out which ports are used by WLM, and open these on the E1000, might this solve the problem? We also tried using WLM from a different computer that uses the E1000 for internet access, and the same problem occurred.

Follow this link to find the port numbers used by Windows Live messenger.
Open these ports on your router and see if that works.

Not connected to internet when using vpn

Hi all - new to MACs and having a couple of problems ...... when I connect to internet using built in ethernet no problems .. when i connect with vpn(pptp) I gt te message connected to server but when i open safari and ty to connect to webpages i get the message that i am not connected to the internet - any help would be appreciated
Pete

on the internet configuration for your vpn connection goto the menu bar and choose connect menu then from the drop down choose 'options' and uncheck 'send all traffic over VPN connection'

Cannot connect to camera when using gpu rendering

Hi, anyone know why I can't connect to the camera when I use gpu rendering. I can use the camera when I use direct. Thanks!

Is this mobile or desktop, or both? Direct is a very preferable option anyhow, FYI. It's required to use Stage3D in many engines as they make clear in all their requisites.

Connection closed error when using binding

Hi,
I am running WLS 7.0.1.0 with TopLink 9.0.3 as the persistence layer for
EJB1.1 beans with CMP. When I use bind parameters I get a connection
closed exception the second time the query is invoked.
This is the query I see on server console when it is invoked the first
time. This query returns the expected results:
[TopLink]: ServerSession(91035)--Connection(887977)--SELECT
LAST_CHANGED_ID, ALIAS_NAME, REFERENCE_ID, ALIAS_TYPE,
REFERENCE_QUAL_CODE, ALIAS_QUAL_CODE, TLINK_VERSION, LAST_CHANGED_DATE,
DELETED_FLAG FROM GLOBAL_ALIAS WHERE (DELETED_FLAG =
bind => [N]
However, when I run the same query the second time I get the
following error:
[TopLink Error]: ServerSession(91035)--Connection(0)--null--EXCEPTION
[TOPLINK-4002] (TopLink (WLS CMP) - 9.0.3.1 (Build 426)):
oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Connection has already
been closed.
INTERNAL EXCEPTION: java.sql.SQLException: Connection has already been
closed.
ERROR CODE: 0
Then when I execute the query again the third time I see the following
sql query and it
works fine.
[TopLink]: ServerSession(91035)--Connection(889939)--SELECT
LAST_CHANGED_ID, ALI
AS_NAME, REFERENCE_ID, ALIAS_TYPE, REFERENCE_QUAL_CODE, ALIAS_QUAL_CODE,
TLINK_V
ERSION, LAST_CHANGED_DATE, DELETED_FLAG FROM GLOBAL_ALIAS WHERE
(DELETED_FLAG =
bind => [N]
Does WebLogic close its connection to the database pool after each
transaction? Is there something that needs to be done on the database?
Any help will be greatly appreciated.
Thanks in Advance,
Anup.

Hi. Our transaction coordinator does prevent any code from using a
pool connection that was part of a transaction, after that transaction
ends. Applications must obtain and use pool connections totally
within or totally outside a UserTransaction, to prevent unintended
or unclear interference of the transaction contents and/or locking.
Joe Weinstein
PS: Also post any followup to the ejb newsgroup, because this issue
is more at the EJB level than JDBC.
Anup Vachali wrote:
Hi,
I am running WLS 7.0.1.0 with TopLink 9.0.3 as the persistence layer for
EJB1.1 beans with CMP. When I use bind parameters I get a connection
closed exception the second time the query is invoked.
This is the query I see on server console when it is invoked the first
time. This query returns the expected results:
[TopLink]: ServerSession(91035)--Connection(887977)--SELECT
LAST_CHANGED_ID, ALIAS_NAME, REFERENCE_ID, ALIAS_TYPE,
REFERENCE_QUAL_CODE, ALIAS_QUAL_CODE, TLINK_VERSION, LAST_CHANGED_DATE,
DELETED_FLAG FROM GLOBAL_ALIAS WHERE (DELETED_FLAG =
bind => [N]
However, when I run the same query the second time I get the
following error:
[TopLink Error]: ServerSession(91035)--Connection(0)--null--EXCEPTION
[TOPLINK-4002] (TopLink (WLS CMP) - 9.0.3.1 (Build 426)):
oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: Connection has already
been closed.
INTERNAL EXCEPTION: java.sql.SQLException: Connection has already been
closed.
ERROR CODE: 0
Then when I execute the query again the third time I see the following
sql query and it
works fine.
[TopLink]: ServerSession(91035)--Connection(889939)--SELECT
LAST_CHANGED_ID, ALI
AS_NAME, REFERENCE_ID, ALIAS_TYPE, REFERENCE_QUAL_CODE, ALIAS_QUAL_CODE,
TLINK_V
ERSION, LAST_CHANGED_DATE, DELETED_FLAG FROM GLOBAL_ALIAS WHERE
(DELETED_FLAG =
bind => [N]
Does WebLogic close its connection to the database pool after each
transaction? Is there something that needs to be done on the database?
Any help will be greatly appreciated.
Thanks in Advance,
Anup.

WRT310N Connection is horrible when using WPA

Similar Messages

Maybe you are looking for