Random timeouts on queries in weblogic

We are using WL 5.1 with SP 9 and jdk1.2.2 oracle thin client classes12_01.zip
We have been having a weird situation where randomly the requesting
thread will be timed out within a request. This same request
works thousands of other times. There is no load on the db and
the network is fine (we ran packet tracing over the interval in question).
The server threw a 300s timeout and the thread was stopped in the
middle of the request, ie no exception was thrown in the requested thread.
Note action that died was outside of the stateless sessino bean in a jdbc query
Any thoughts?

Jen:
All beans will timeout as defined by the timeout for the session.
Weblogic monitors the request duration on the thread and will time
it out if it does not finish within a certain time. Not anything to do
with a db transaction as such.
We are experiences an issue we think when the transaction dies
but does not unlock the lock for the ejb.
Philip.
"Jen " <[email protected]> wrote in message
news:[email protected]...
>
I am curious that if your stateless session bean got time out exception. Ihad a problem
that stateless session bean call helper class, and helper class connect todb (no
TX), and got couple time that ejb time out, after time out the processcontinued
which is around where the db operation happens. I still don't know dbcaused ejb
timed out or ejb hung and blocked the process
[email protected] (Philip) wrote:
Thanks Alex,
I have pulled down the latest 1.7 classes.zip and we
are running this through testing now. The biggest problem
we have had is being able to reproduce this. It is very random.
There were no database issues during the period in question
we monitor it for locks as well as waits.
Philip.
"AV" <[email protected]> wrote in message
news:<[email protected]>...
Previously, in this newsgroup, people reported
strange 60 sec delays from Oracle. General advice
is to update the driver (Oracle keeps the same name
classes12.zip, but actually updates it regularly).
Also, ask your DBA check what database is doing
in such moments: deadlock? system processes running?
nothing? waiting for something from somewhere?
AlexV.
"Philip" <[email protected]> wrote in message
news:[email protected]...
We are using WL 5.1 with SP 9 and jdk1.2.2 oracle thin clientclasses12_01.zip
We have been having a weird situation where randomly the requesting
thread will be timed out within a request. This same request
works thousands of other times. There is no load on the db and
the network is fine (we ran packet tracing over the interval in
question).
The server threw a 300s timeout and the thread was stopped in the
middle of the request, ie no exception was thrown in the requestedthread.
Note action that died was outside of the stateless sessino bean in ajdbc
query
Any thoughts?

Similar Messages

Queries about weblogic server

hi,
can someone please provide answers for following queries
Does Weblogic has something called ?Administration Mode? and if answer is yes does it also report web logic service as ?not running?.
can we take Weblogic backup and if answer is yes what do we backup?
When can we say that web logic is unstable?
thanks
ajay

ajay prabhu <> wrote:
hi,
can someone please provide answers for following queries
Does Weblogic has something called ?Administration Mode? and if answer is
yes does it also report web logic service as ?not running?. Euh... via the administration server you can see if an
application/server/etc is running or not.
can we take
Weblogic backup and if answer is yes what do we backup? The config directory + the application itself are important
When can we say
that web logic is unstable?If it crashes :)
Schelstraete Bart
http://www.schelstraete.org
Linkedin: http://www.linkedin.com/in/bschelst

Timeout waiting for Oracle WebLogic Server v10.3 at localhost to start

I am trying to run .portal file using "Run on server" option in Workshop for weblogic.
After doing this, its trying to start the server Oracle weblogic server v10.3 at localhost and then publish my module.
Server view status shows as "State" as "Starting" and "Status" as "Synchronizing". When status reaches 82% it gets stopped there for a long time, and when 83% comes up, I can see the "State" as "Stopped" and "Status" as "Republish". And then an error window with title as "Problem Occured" and contents saying, Starting server- Oracle weblogic server v10.3 at localhost (Time of error: ...) Details >> Timeout waiting for Oracle WebLogic Server v10.3 at localhost to start. Server did not start after 480s.
But the console tab (when I give the startup & Deployment option as "Launch Weblogic server in eclipse console) shows,
<Sep 8, 2011 6:15:03 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
e changed to STARTING> (final step alone I pasted)
Before this I can see, WLS Start mode = Development, setting Classpath ,
<Sep 8, 2011 5:56:36 PM IST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\bea\user_projects\domains\myPortalDomain\servers\AdminServer\logs\Ad
minServer.log is opened. All server side log events will be written to this file
.>
When I checked Adminserver file its having,
<AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1315487671986> <BEA-160151> <Registered library Extension-Name: wlp-groupspace-app-lib, Specification-Version: 10.3, Implementation-Version: 10.3.0.1 (EAR).>
And many more similar entries...
Also there is Adminserver.logxxx file which is having,
####<Sep 8, 2011 5:33:58 PM IST> <Warning> <JDBC> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1315483438048> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Sep 8, 2011 5:33:58 PM IST> <Info> <JDBC> <CINTNCHEOLY0GX7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1315483438267> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
     at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
     at com.pointbase.net.netJDBCConnection.a(Unknown Source)
     at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
     at com.pointbase.net.netJDBCDriver.getConnection(DashoA10*..:170)
     at com.pointbase.net.netJDBCDriver.connect(DashoA10*..:94)
     at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
     at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:316)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:217)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
     at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2282)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
And many more entries like the above...
I even tried startup & Deployment option as "Start weblogic server in Expressmode" and still same error I am getting and this time instead of in eclipse console, I can see command prompt and here also showing "Server state changed to STARTING"
FYI, I created domain with runtime JRocket 1.6.0_05.
I even tried to clean build the portal project and publish using clean option. Still same problem coming :(
FYI, my system is having 1 GB RAM only and bit slow. Could this be a problem or something else? Please suggest.
Thanks in advance.
Edited by: gopikrish on Sep 8, 2011 6:20 AM

Hi Gopikrish
The root cause for your error is, it is not able to start the Pointbase database. Looks like you configured a domain with default pointbase database. In the domain\bin\ one of the starup scripts like startWeblogic.cmd, you should see some lines that start the pointbase database.
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093
Instead of starting from Workshop, go to the domain root folder and start the weblogic using the command like startWeblogic.cmd (or .sh on unix). This should start the pointbase and then start the portal domain. Portal domain does need this backend pointbase database to store all the portal meta data and has datasources configured for this.
Do you have a Clustered Portal domain, with one of the managed servers located in the remote machine. If yes, and if you use default Pointbase database, you need to change something like pointbase db should not be localhost but the name of the machine where you have the admin server running.
Either way, the issue is not able to stat the pointbase db and thus serve not starting.
Thanks
Ravi Jegga

Random timeout with digital sign, DocumentManagerClient.java:329

hey guys,
Not sure if any one of you have similar experience. We are running Livecyle.ES 8.2.1 and so far we use this for signing PDF files only for a government agency.We use EJB endpoint.
Our application is a custom webapp which use Livecycle Java AIP. The problem we see is on and off, we see this exception during sign PDF.
2009-04-04 10:37:50,420 ERROR [STDERR] Apr 4, 2009 10:37:50 AM com.adobe.idp.DocumentManagerClient requestRemotePassivation
SEVERE: DOCS001: Unexpected exception. See the stack trace for details.
org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 208 completed: Maybe
    at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectionAbort(ORBUtilSystemExcepti on.java:2372)
And this error is raised from,
com.adobe.idp.DocumentError: org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 208 completed: Maybe
    at com.adobe.idp.DocumentManagerClient.requestRemotePassivation(DocumentManagerClient.java:32 9)
    at com.adobe.idp.Document.passivate(Document.java:1069)
    at com.adobe.idp.Document.passivate(Document.java:1012)
    at com.adobe.idp.Document.getInputStream(Document.java:1524)
The interesting this about this error is, documents get signed before and after this error, are just fine. This problem used to last about 1 minute and gone. And this happens only in our PROD env . I dont see this in my DEV or TEST. The tricky thing is, in PROD, we connect to a hardware signature profile, rather than a normal scenario, not sure if related.
My guessing is that the document do get signed on the server side, and then somehow when client request it, it is gone or something.
Well, i am stomped. Really appreciate if anyone of you can share some insight.
Thanks.
-ying

Well, after a week's test I have a walkaround for this problem, I changed code to use SOAP endpoint instead of EJB. I have to do this for another reason.
My application is a webservice running under another JBoss instance. Before, I have to restart JBoss, each time, if Livecycle get bounced. This, I guess has to do with ServiceFactory cached javax.naming.InitialContext. Once Livecycle get bounced, the InitialContext get obsolete. The good part of using a SOAP endpoint is, I dont need bounce my JBoss any more.
After I made the switch, this old random timeout problem seems like going away. I still not fully understand the reason. One thing is a fact that for EJB, I have to get permission to open 1099 port through firewall (two of them). But, for SOAP, 8080 also need be opened. I am not a network kind of person, maybe HTTP is treated differently?
Well, well, as long as I dont see the problem, I let it go ...
-ying

BAM getting random timeouts calling BPEL web service as alert rule

I have a BAM alert rule set up to call a BPEL process (web service call basically). This is part of our custom error notification and escalation solution.
In production I randomly see timeouts in the BAM event engine logs where the web service call has timed out. On the BPEL side these processes never show as being invoked, nor are they in manual recovery.
This only happens at random times, although usually in "clumps" lasting a few minutes. The rest of the time this has been fairly reliable.
Any help from the BAM experts would be appreciated. I would open an SR on this, but I have found support to literally take days/weeks to get back to me on BAM issues -- and this particular issue does not seem to be reliably reproduceable.
Here is the event engine log message:
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11309)] ERROR - EventEngine Action exception: EEInstEv218067 EEInstAct218066 Rule Id: 1 exception: The operation has timed-out. (http://mcsbpel:8888/orabpel/MAEF/svcMaefErrorAlert/1.0)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11304)] ERROR - EventEngine Action exception: EEInstEv218066 EEInstAct218065 Rule Id: 1 exception: The operation has timed-out. (http://mcsbpel:8888/orabpel/MAEF/svcMaefErrorAlert/1.0)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11309)] WARN - EventEngine Exception stack trace: at Oracle.BAM.Middleware.EventEngine.ExternalActions.WebServiceCaller.TakeAction(Hashtable oParameters, String strDataObject, Hashtable oDataValues, Hashtable oDataTypes)
at Oracle.BAM.EventEngine.Actions.TakeExternalAction.TakeAction(String strSysIterID, Hashtable oParameters, String strDatasetName, XmlDocument xmlSchemaDoc, IDictionary intDataDictionary)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ExternalAction(ActionQueueItem oActionQueueItem)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ActionHandler(Object state, DateTime requestEnqueueTime)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11304)] WARN - EventEngine Exception stack trace: at Oracle.BAM.Middleware.EventEngine.ExternalActions.WebServiceCaller.TakeAction(Hashtable oParameters, String strDataObject, Hashtable oDataValues, Hashtable oDataTypes)
at Oracle.BAM.EventEngine.Actions.TakeExternalAction.TakeAction(String strSysIterID, Hashtable oParameters, String strDatasetName, XmlDocument xmlSchemaDoc, IDictionary intDataDictionary)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ExternalAction(ActionQueueItem oActionQueueItem)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ActionHandler(Object state, DateTime requestEnqueueTime)

I should note that both BPEL and BAM are at version 10.1.3.1

Deployment error - Errors in named queries in weblogic 10

Hi, All.
I got the error message when I tried to deploy my webapp to weblogic 10 & 10.1(10M1).
Stacktrace:
<May 19, 2008 11:51:14 AM EDT> <Error> <Console> <BEA-240003> <Console encounter
ed the following error weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:314)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedM
oduleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: java.lang.Throwable: Substituted for missing class org.hibernate.Hibe
rnateException - Errors in named queries: SpotType.findById, Spot.findByTopic, T
argetAudience.findById, SpotOrder.findById, SpotAuditDetails.findById, ProjectOf
ficer.findById, SpotOrderAvailable.findById, ProjectOfficer.findByStatus, SpotOr
derTopic.findById, Topic.findById, findAllSpots, SpotOrderDetails.findById, find
AllCategory, SME.findById, SpotAudit.findById, ContactInfo.findById, SpotCategor
y.findById, SpotOrderTopicSpot.findById, ProjectTopic.findById, NetworkType.find
ById, Source.findById, NetworkType.findByStatus, RecordStatus.findById, SpotType
.findByStatus, findAllClient, Spot.findByTitle, findAllRecordStatus, SMETopicCom
ments.findById, ContractInfo.findById, Channel.findById, Client.findById, findAl
lSource, SMETopic.findById, Project.findById, SpotComments.findById, SpotOrderCo
mments.findById, ContactInfoComments.findById, Spot.findById
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:
365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.jav
a:1300)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(Annotat
ionConfiguration.java:859)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
figuration.java:669)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFa
ctory(HibernatePersistence.java:132)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactor
y(PersistenceUnitInfoImpl.java:264)
at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInf
oImpl.java:110)
at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(
AbstractPersistenceUnitRegistry.java:316)
at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDe
scriptors(AbstractPersistenceUnitRegistry.java:96)
at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersis
tenceUnitRegistry.java:53)
at weblogic.servlet.internal.WebAppModule.initPURegistry(WebAppModule.ja
va:1151)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:304)
>
I included named queries on orm.xml file and also in each entities using annotations like following.
orm.xml>
<?xml version="1.0" encoding="UTF-8"?>
<entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
     version="1.0">
     
     <named-query name="findAllClient">
<query><![CDATA[SELECT e FROM Client e ORDER BY e.clientName]]></query>
</named-query>
<named-query name="findAllSource">
<query><![CDATA[SELECT e FROM Source e ORDER BY e.sourceDesc]]></query>
</named-query>
<named-query name="findAllCategory">
<query><![CDATA[SELECT e FROM SpotCategory e ORDER BY e.spotCategoryDesc]]></query>
</named-query>
<named-query name="findAllRecordStatus">
<query><![CDATA[SELECT e FROM RecordStatus e ORDER BY e.id]]></query>
</named-query>
<named-query name="findAllSpots">
<query><![CDATA[SELECT e FROM Spot e ORDER BY e.id]]></query>
</named-query>
</entity-mappings>
entity example:
@Entity
@Table(name = "SPOTTYPE")
@NamedQueries( { @NamedQuery(name = "SpotType.findById", query = "SELECT e FROM SpotType e WHERE e.id = :id"),
     @NamedQuery(name = "SpotType.findByStatus", query = "SELECT e FROM SpotType e WHERE e.recordStatus.id = :status") })
public class SpotType implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(generator = "spotTypeSeq")
@SequenceGenerator(name = "spotTypeSeq", sequenceName = "SEQ_SPOTTYPE", allocationSize = 1)
@Column(name = "SPOTTYPEID", nullable = false, length = 2)
private Long id;
@Column(name = "SPOTTYPESHRTNM", nullable = false, length = 2)
private String spotTypeShortName;
@Column(name = "SPOTTYPELONGNM", nullable = false, length = 35)
everything works until I clicked the activate the change button. I tried to override libs by putting libs I'm using in my domain, still I have the same error message.
Libs that I have:
Name 5 Size Type Date Modified
antlr-2.7.6.jar 434 KB ALZip jar File 2/13/2008 5:28 PM
asm.jar 26 KB ALZip jar File 2/13/2008 5:28 PM
asm-attrs.jar 17 KB ALZip jar File 3/17/2005 4:05 PM
cglib-2.1.3.jar 276 KB ALZip jar File 2/13/2008 5:28 PM
commons-beanutils-1.7.0.jar 185 KB ALZip jar File 12/15/2007 7:12 PM
commons-codec-1.3.jar 46 KB ALZip jar File 12/15/2007 7:12 PM
commons-collections-3.1.jar 547 KB ALZip jar File 4/24/2008 10:28 AM
commons-digester-1.8.jar 141 KB ALZip jar File 12/15/2007 7:13 PM
commons-discovery-0.4.jar 75 KB ALZip jar File 12/15/2007 9:08 PM
commons-el-1.0.jar 110 KB ALZip jar File 5/15/2008 1:11 PM
commons-logging-1.0.4.jar 38 KB ALZip jar File 7/4/2004 4:49 AM
dom4j-1.6.1.jar 307 KB ALZip jar File 2/13/2008 5:28 PM
ehcache-1.2.jar 116 KB ALZip jar File 2/13/2008 5:28 PM
ejb3-persistence.jar 52 KB ALZip jar File 3/14/2008 4:45 PM
hibernate3.jar 2,222 KB ALZip jar File 2/6/2008 9:31 PM
hibernate-annotations.jar 274 KB ALZip jar File 3/14/2008 4:44 PM
hibernate-commons-annotatio... 65 KB ALZip jar File 3/14/2008 4:45 PM
hibernate-entitymanager.jar 116 KB ALZip jar File 3/14/2008 8:07 PM
jaas.jar 102 KB ALZip jar File 6/3/2004 11:31 AM
javassist.jar 449 KB ALZip jar File 2/13/2008 5:28 PM
jaxen-1.1-beta-7.jar 222 KB ALZip jar File 8/16/2005 2:04 PM
jboss-archive-browsing.jar 13 KB ALZip jar File 2/13/2008 5:28 PM
jhighlight-1.0.jar 92 KB ALZip jar File 12/20/2007 4:51 PM
jsf-facelets.jar 294 KB ALZip jar File 9/27/2007 12:20 PM
jstl-1.2.jar 405 KB ALZip jar File 5/15/2008 1:12 PM
jta.jar 9 KB ALZip jar File 6/3/2004 11:31 AM
junit-4.4.jar 158 KB ALZip jar File 5/15/2008 1:12 PM
log4j-1.2.11.jar 343 KB ALZip jar File 8/13/2005 3:28 PM
myfaces-api-1.2.2.jar 319 KB ALZip jar File 1/22/2008 3:40 PM
myfaces-impl-1.2.2.jar 739 KB ALZip jar File 1/22/2008 3:40 PM
nekohtml-0.9.5.jar 104 KB ALZip jar File 12/20/2007 4:42 PM
ojdbc14.jar 1,322 KB ALZip jar File 2/13/2008 5:30 PM
readme.txt 1 KB Text Document 5/15/2008 3:58 PM
richfaces-api-3.2.0.GA.jar 150 KB ALZip jar File 3/31/2008 4:23 PM
richfaces-impl-3.2.0.GA.jar 1,372 KB ALZip jar File 3/31/2008 4:23 PM
richfaces-ui-3.2.0.GA.jar 2,215 KB ALZip jar File 3/31/2008 4:50 PM
spring.jar 2,604 KB ALZip jar File 5/15/2008 1:12 PM
xerces-2.6.2.jar 988 KB ALZip jar File 12/19/2004 6:14 PM
xml-apis.jar 121 KB ALZip jar File 6/3/2004 11:31 AM
This can be deployed to tomcat 6 without any problems.
Thank you in advance for reading and your help.
Edited by gzson at 05/19/2008 9:07 AM

Follow the below link:
http://www.hibernate.org/250.html#A25

Executing Store Procedure random timeouts

We have some simple stored procedures that run find when run under the Advantage Data Architect, but randomly times out when we call them from our ASP web site using the OLEDB driver.
When we try to call them using the Advantage Java database driver we get and error code 9105 SQL state S0000 error with no descripive message.
Does anyone have any insights into either of these issues?
Dave Anderson

Your stored procedure only takes Milliseconds to finish normally?
How do you know it is timing out? The default is 30 seconds so seeing it timeout I would have assumed it was a longer running one. Are you getting the ADS error 7209 back or Run-Time error
'3712' Operation has been cancelled by the user?
It's been ages since I've looked at VB, but I think it should be something like this
cmd = New ADODB.Command
cmd.CommandText = "execute procedure ....."
cmd.CommandType = adCmdText
cmd.CommandTimeout = 0
rs = cmd.Execute
For the JDBC issue, it is difficult to tell by the date, but I think that date indicates likely a 10.x or 11.x driver. The issue I was thinking of I believe was fixed in 9.x.
You can try the latest 11.1 version (11.10.0.20) as I think that was released in July of this year. Maybe it will help? If not a support incident would be a good idea (particularly if you can duplicate it)
Out of curiosity are you using the varying output type stored procedures? (Not that I have anything to offer as a workaround, but the error is indicating there was a problem retrieving column informaiton and this is the only thing I can think of off the top of my head).
Edgar

Asmx Web Service Random Timeout on SSL Handshake

We have an asmx web service that is deployed on a server farm with two servers (both Virtual Machines with Windows 2008). The asmx web service, when invoked from a .net client application randomly returns this error:
"The underlying connection was closed: An unexpected error occurred on a receive."
On a retry, the operation works fine. But the problem recurs after a few tries.
When I tried to trap this message in Fiddler, this was the error:
HTTP/1.1 200 Connection Established
FiddlerGateway: Direct
StartTime: 17:23:35.494
Connection: close
fiddler.network.https> HTTPS handshake to <removed the site name> failed. System.IO.IOException Unable to read data from the transport connection: An existing connection
was forcibly closed by the remote host. < An existing connection was forcibly closed by the remote host.
One thing that is noticeable is that all "random" errors occur only if when the client "tunnels" to site as per Fiddler. Sometimes the "tunnel" succeeds and sometimes it fails.
This server farm is behind an F5 load balancer.
I also have a replacement for this asmx web service which is a WCF service. That service is also deployed on the same server farm. This WCF service also gets the same random error though it does not seem to be that frequent. I have tried to trace the error
message on the client and the server and nothing seems to work so far.
I am working with a Microsoft support person and a network expert on this issue.
I am posting this question to the community to see if anybody else ran into a similar issue and if yes, what were their findings?
Thanks in advance for your help.

This issue turned out to the related to the virtual network interface card on one of the two servers that were part of the load balanced pool. Once we created a new NIC and reassigned the website IP addressed to it, the problem went away.
I'd like to document what I learnt from the troubleshooting exercise. This is probably already documented on various forums but just thought I'll share this information.
1. Troubleshooting Steps on the server:
a. Make sure the URL of the WCF service shows up fine on a web browser on the client and the server. In many cases, the issue with the WCF service shows up in the browser window itself.
b. Take a look at SSL certificates and make sure those are installed correctly. Drop a test html file with hello world message in the web root folder of the server and see if your client browser can access it with SSL without any warnings or errors. Refresh
the page multiple types to see if you get a random error.
c. Enable WCF tracing on both the client and the server.
https://msdn.microsoft.com/en-us/library/ms733025(v=vs.110).aspx
d. If the traces do not provide any useful info, install Netmon on the client and the server and look at Netmon traces.
http://www.microsoft.com/en-us/download/details.aspx?id=4865
Apparently, there is a newer tool called 'Microsoft Message Analyzer' (http://www.microsoft.com/en-us/download/details.aspx?id=44226) but I did not use this tool.
e. Install Fiddler or Wireshark on the client and the server and monitor network traffic.
2. We learnt from the Netmon traces that the load balancer was dropping packets randomly when connecting to one of the two servers. So we removed the server that was working fine from the load balanced pool and tested just with the 'erroring' server. We
placed a test.html file on the web root of the server and continued our testing. We noticed that the random errors were evident also in non-SSL communication. So this eliminated the theory that the WCF service or the SSL certificates that anything to do with
the random error. We noticed that the server would respond for a few minutes and then started dropping TCP packets. Once we added the virtual NIC, the problem went away.
3. Our third option would be to remove the load balancer from the picture but that was not needed once we figured out the issue in step 2.
Hope this information helps someone else who is facing or will face a similar problem.

Dynamic queries in weblogic

In case of dynamic queries, I found out that the finder method can not be defined
in the Home class. I defined the finder
method in the Bean.
In my Bean, this is the code:
public Collection findAllActivities(String filter, Object[] arguments) throws
FinderException
     Properties myProp = new Properties();
     for(int i = 0; i < arguments.length; i++)
          myProp.setProperty(String.valueOf(i), String.valueOf((arguments)));
     try
          InitialContext ic = new InitialContext();
          RolesHome rh = (RolesHome)ic.lookup("RolesHome");
          QueryHome qh = (QueryHome)rh;
          String weblogicQL = "SELECT DISTINCT OBJECT(o) FROM roles AS o" + filter;
          Query query = qh.createQuery();
          return query.find(weblogicQL, myProp);
     catch (Exception e)
          e.printStackTrace();
          return null;
I get a naming exception if I use :      RolesHome rh = (RolesHome)ic.lookup("RolesHome");
javax.naming.NameNotFoundException: Unable to resolve 'RolesHome' Resolved: ''
Unresolved:'RolesHome' ; remaining name
'RolesHome'
I get a casting exception if I use:      RolesHome rh = (RolesHome)ic.lookup("Roles");
In my jsp file:
I have this code
InitialContext jndiContext = new InitialContext();
Object obj = jndiContext.lookup("Roles");
RolesHome rolesHome = (RolesHome) obj;
list = (ArrayList) rolesHome.findAllActivities(filter, filterParams);
but the problem is that the home interface does not contain the findAllActivities
function. I have already defined rolesHome
earlier in the code which I want to use for findAllActivities also. I can not
cast the bean e.g. RolesBean rolesBean = (
RolesBean) rolesHome. I do not want to create a new bean as I am already using
an old rolesHome. How do I solve this
problem??? Please do let me know. I am really confused.
Thanks
Ronak Parekh

This should be posted to the ejb newsgroups
mbg
"ronak" <[email protected]> wrote in message
news:3e57faa9$[email protected]..
>
In case of dynamic queries, I found out that the finder method can not bedefined
in the Home class. I defined the finder
method in the Bean.
In my Bean, this is the code:
public Collection findAllActivities(String filter, Object[] arguments)throws
FinderException
Properties myProp = new Properties();
for(int i = 0; i < arguments.length; i++)
myProp.setProperty(String.valueOf(i), String.valueOf((arguments)));
try
InitialContext ic = new InitialContext();
RolesHome rh = (RolesHome)ic.lookup("RolesHome");
QueryHome qh = (QueryHome)rh;
String weblogicQL = "SELECT DISTINCT OBJECT(o) FROM roles AS o" + filter;
Query query = qh.createQuery();
return query.find(weblogicQL, myProp);
catch (Exception e)
e.printStackTrace();
return null;
I get a naming exception if I use : RolesHome rh =
(RolesHome)ic.lookup("RolesHome");
>
javax.naming.NameNotFoundException: Unable to resolve 'RolesHome'Resolved: ''
Unresolved:'RolesHome' ; remaining name
'RolesHome'
I get a casting exception if I use: RolesHome rh =(RolesHome)ic.lookup("Roles");
>
>
In my jsp file:
I have this code
InitialContext jndiContext = new InitialContext();
Object obj = jndiContext.lookup("Roles");
RolesHome rolesHome = (RolesHome) obj;
list = (ArrayList) rolesHome.findAllActivities(filter, filterParams);
but the problem is that the home interface does not contain thefindAllActivities
function. I have already defined rolesHome
earlier in the code which I want to use for findAllActivities also. I cannot
cast the bean e.g. RolesBean rolesBean = (
RolesBean) rolesHome. I do not want to create a new bean as I am alreadyusing
an old rolesHome. How do I solve this
problem??? Please do let me know. I am really confused.
Thanks
Ronak Parekh

Queries on WebLogic JMS

Hi,
I'm learning JMS on WebLogic 10.3.4, and I've got the following questions that have been puzzling me:
1. How do I link one or more queues/topics to a single connection factory, so that they may be accessible only via that connection factory and no other?
2. How do I provide a username/password security to a JMS connection factory and a JMS queue?
I'd appreciate any insight on the matter.

You can use the "security" section of the administration console to secure all destinations in a particular JMS configuration module, or even particular destinations within a module.
There is no direct facility for securing a connection factory, nor is there usually a need, as destinations can be secured. Never-the-less, you can indirectly limit access to a connection factory by securing it's JNDI name. Any JNDI name can be secured (not just JMS artifacts). I don't know how this is done.
Note that WebLogic JMS does little with the username and password that you can pass to the "createConnection()" calls in the JMS API. Instead, it uses the credential that's been established on the current thread. There are various ways to set the credential on the current thread: automatically in server containers via various configuration options, or by creating an "InitialContext" with a user/pass in the same thread on a client...
Hope this helps,
Tom

Transaction Timeout (BPEL v10.1.2.0.0, WebLogic 8.1 sp4)

We are attempting to process a transform on a medium sized xml doc (~4.5 MB). For the test case we are simply reading the the doc using the FileAdapter, performing a transformation, and then writing the result to a file using the FileAdapter once again. The flow works fine for smallish files (under ~4MB), however, when dropping a file greater than that size the flow fails once finished while writing entries to the BPEL audit log with a TransactionTimedOutException (see exception below).
I understand what is happening and why (it certainly takes longer than 2 mins to process the file). I have also done quite a bit of digging around for references to this issue and found several posts regarding bumping the transaction timeout value when running the OC4J container. My problem is that we are not running the OC4J container. I know how to manage the default transaction timeout value for WebLogic but it appears that the BPEL application doesn't seem to be honoring the default transaction timeout on the WL Server. I have come to this conclusion for two reasons: first, the default transaction timeout on the WL Server (before modification) is 30 seconds, not the 120 seconds that this transaction is timing out on. second, changing the transaction timeout value on the WebLogic server has no impact on this issue what so ever. I can set the transaction timeout to any value I like, the process ALWAYS times out after 120 seconds.
Is there another setting on the BPEL server that I may have missed that is overriding the default timeout, i.e. is it possible that when the BPEL server process is starting the transaction it is setting the timeout on the TransactionManager in code prior to starting the transaction?
Any pointers are greatly appreciated.
------------- START STACK TRACE ------------------
<2007-03-15 13:50:24,625> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Cannot insert audit trail.
The process domain was unable to insert the current log entries for the instance "10601" to the audit trail table. The exception reported is: The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)]'. No further JDBC access is allowed within this transaction.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usize, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
<2007-03-15 13:50:24,643> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1614)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1117)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1881)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1034)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
------------- END STACK TRACE ------------------

Hi
i am facing a similar problem..did u find the solution for this problem?
Please pass the solution/workaround u performed for solving this...
Thanks & Regards
Subramanian

Weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000' ms

Hi All,
Again, Since yesterday (11/11/2003) , I started getting the Bean Lock error as
below (I am using weblogic 4.5.1) :
Note: We are using Stateless beans.
Tue Nov 11 14:15:11 CET 2003:<I> <EJB> Transaction: '1068220908390_17748' rolled
back due to EJB exception:
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1866)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Tue Nov 11 14:15:11 CET 2003: ERR #-3# com.sgs.ecertificate.ProcessApproveCertificateServlet
An unexpected error occurs when trying to perform your request (RemoteException).
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:310)
     at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:128)
     at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:182)
     at com.sgs.ecertificate.entity.CertificateEntityBeanEOImpl.getData(CertificateEntityBeanEOImpl.java:4645)
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1743)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Thanks a lot in advance.
Regards,
Nilesh.

Hi All,
Again, Since yesterday (11/11/2003) , I started getting the Bean Lock error as
below (I am using weblogic 4.5.1) :
Note: We are using Stateless beans.
Tue Nov 11 14:15:11 CET 2003:<I> <EJB> Transaction: '1068220908390_17748' rolled
back due to EJB exception:
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1866)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Tue Nov 11 14:15:11 CET 2003: ERR #-3# com.sgs.ecertificate.ProcessApproveCertificateServlet
An unexpected error occurs when trying to perform your request (RemoteException).
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:310)
     at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:128)
     at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:182)
     at com.sgs.ecertificate.entity.CertificateEntityBeanEOImpl.getData(CertificateEntityBeanEOImpl.java:4645)
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1743)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Thanks a lot in advance.
Regards,
Nilesh.

Random 504 Timeout Errors

Running BM 3.8 on a NW 6.5 SP7 box. Proxy.cfg from Craig J. is loaded. We get random timeouts on 504 errors, mainly with this one site Education 2020 - Web Administrator. So far, the only thing I've found common among the timeouts is that the site uses Javascript. We've tried the obvious --rebooting, cleaning cache, etc all to no avail. Are there some more settings we need to tweak or configure to get these sites to work? We use transparent proxy on our site as well.

Originally Posted by phxazcraig
In article <[email protected]>, Apsfalcons
wrote:
> By "targeted filter exception", do you mean the "non-cacheable object
> control"
> Otherwise, please let me know what you mean by that. Also, we DO have
> the browser set to "not" proxy the URL in question.
>
No, I mean the IP address of the server, and the port number(s)
involved, in one or more filter exceptions. (To allow people to bypass
the proxy and just go out through nat).
Gotcha. Yes, I have that setup for at least my machine. I still get 504 time outs from border which leads me to believe I'm still somehow passing through transparent proxy? On the BM Setup->Transparent Proxy->Details screen my IP is in the "exception list".

Session Replication and Session Timeout -- Urgent

WLS -4.5.1 SP 11
          OS - both NT and Sol
          HI All
          The session does not seems to timeout when running the Weblogic servers in
          clustered mode with in-memory session replication on.
          This problem seems to be there in version5.1 too , as per another post , it
          seems to be solved in WLS5.1 sp 8
          Could anyone pls confirm in which patch in WLS 4.5.1 is the problem
          addressed . I'm using patch 11 and am getting the problem.
          Thanks in advance..
          -Surya


Try SP13 and if the problem persists, contact [email protected]
          -K
          Surya B Maithani wrote:
          > WLS -4.5.1 SP 11
          > OS - both NT and Sol
          >
          > HI All
          >
          > The session does not seems to timeout when running the Weblogic servers in
          > clustered mode with in-memory session replication on.
          > This problem seems to be there in version5.1 too , as per another post , it
          > seems to be solved in WLS5.1 sp 8
          >
          > Could anyone pls confirm in which patch in WLS 4.5.1 is the problem
          > addressed . I'm using patch 11 and am getting the problem.
          >
          > Thanks in advance..
          >
          > -Surya

Web service client timeout

Hi,
I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
I am using weblogic 10.3.2, with Java 1.6.
============
Properties propSys = System.getProperties();
propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
Stub stub = (Stub)portObject;
BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(1);
Iterator itr = stub._getPropertyNames();
while (itr.hasNext()){
Object element = itr.next();
log("\n properties that can be set: "+element);
stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
===========
I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
===========
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ExternalEntryEJB</ejb-name>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>ExternalEntry</jndi-name>
<remote-client-timeout>1</remote-client-timeout>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>InternalEJB</ejb-name>
<local-jndi-name>Internal</local-jndi-name>
<enable-call-by-reference>True</enable-call-by-reference>
<remote-client-timeout>1</remote-client-timeout>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
===========
in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
============
<clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
<classpath refid="build.classpath.builddir"/>
</clientgen>
============
I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
Thanks,
Walter

Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
<taskdef name="clientgen"
classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
Hope that helps.

Random timeouts on queries in weblogic

Similar Messages

Maybe you are looking for