JMS timeout and redelivery

I have two simple questions:
1. Let's suppose a situation when a table lock is present in our database and the MDB regularly runs into this lock every time when the onMessage method is called. It always reserves a new MDB because the MDB created by the previous call is not capable to move back to the pool becaus of the lock. It means if there is no more free bean in the pool a new bean will be created. Hence a simple database lock can cause application server to run out of system resources.
Is there any way to catch the timeout or how can I avoid this situation?
2. If consumption of the message fails the message is redelivered successively but the reason of the failure is still present. I wouldn't like to lose these failed messages. Do I have to move these to another queue or is there any standard scenario for this kind of situation? Can I delay the redelivery?
Thanks in advance

To the second question, it is dependant of your JMS providers. It may include these configuration parameters to fine-tune redelivery:
* Redelivery count: The number of times to redeliver a message. Redelivery count is important because poison messages, messages the application can never successfully process, can eventually crash the system.
* Exception destination: What happens to a message that is redelivered redelivery-count times? The JMS provider can do any of the following:
o Log the message
o Forward the message to an exception or error destination
o Lose the message
* Time to redeliver: An application that has just rolled back messages might not be ready to reprocess the same messages. This parameter specifies the time to wait before redelivering the message. This delay lets the JMS provider and the application recover to a stable state.
I know that in weblogic, you can specify this parameters when you specify your JMS settings.
Actually I work with BES 5.2.1, and I can not specify this settings. It will be a new feature of BES 6.

Similar Messages

Transaction Session, Rollback and Redelivery

          Well, apparently this is a bug in Weblogic 6.1 up to sp2. (I can not comment if this
          bug either exists or does not exist in 6.0 and below or 7.0 and above.) Bug ID is
          :CR080301 if this is impacting anyone else. I'll post the final outcome and if
          it gets fixed.
          (I would also ask everyone if you post a question and end up going to BEA, customer
          support, if you could post the outcome, that would make everyone's life so much easier.)
          To respond to me via E-mail, simply pull the weeds. =)
          Tom Barnes <[email protected]> wrote:
          >Hi Mike,
          >
          >As far as I know, Zach's response still stands. The behavior you are seeing,
          >given
          >the limited information posted, doesn't ring any bells. Please forward
          >your issue to
          >customer
          >support, with enough information to reproduce along with a SP number and
          >thread-dumps.
          >They will know if your particular problem has been seen before...
          >
          >If you like, post your reproducer code here, with thread-dumps.
          >
          >Tom
          >
          >P.S. Email addresses on this forum tend to be "bogus" because this is not
          >a formal
          >forum. Think of it as a free Anne Landers for JMS. Posters are volunteers,
          >posting
          >on "their own time".
          >
          >Mike Wiles wrote:
          >
          >> Was there ever any outcome to this issue? I am experiencing the same
          >behavior and
          >> since both of these E-mail addresses are pretty much bogus, it is impossible
          >to get
          >> some sort of follow-up.
          >>
          >> Mike
          >>
          >> To send me an E-mail, simply pull the WEEDS.
          >>
          >> "Zach" <[email protected]> wrote:
          >> >Very strange behavior. You should file a support case.
          >> >_sjz.
          >> >
          >> >"Bart Simpson" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> Hi,
          >> >>
          >> >> I am trying to understand, how rollback works with transaction session
          >> >in
          >> >WLS
          >> >> 6.1 sp1. What should happen when session.rollback() is called? After
          >> >calling
          >> >> rollback() couple of times, the server program receiving the messages
          >> >just
          >> >hangs?
          >> >> I have configured redelivery delay to 3000 and redelivery tries to
          >3.
          >> >However,
          >> >> if I restart the server program, then I see the normal redelivery
          >> >happening again.
          >> >> Is this a feature or bug?
          >> >>
          >> >> Here is the client program:
          >> >> package com.malani.jms.client;
          >> >>
          >> >> import java.util.*;
          >> >>
          >> >> import javax.jms.*;
          >> >> import javax.naming.*;
          >> >>
          >> >> import com.malani.jms.resources.*;
          >> >>
          >> >> public class Client {
          >> >>
          >> >> public static void sendMessage(QueueSender aSender, Session aSession,
          >> >int
          >> >> i)
          >> >> throws JMSException
          >> >> {
          >> >> aSender.send(aSession.createTextMessage("" + i));
          >> >> }
          >> >>
          >> >> public static void printUsage() {
          >> >> System.out.println("Usage:");
          >> >> System.out.println(Client.class.getName() + " jndi_queue_name");
          >> >> System.exit(1);
          >> >> }
          >> >>
          >> >> public static void main(String[] args) {
          >> >> if (args.length != 1) {
          >> >> printUsage();
          >> >> }
          >> >>
          >> >> QueueSender aSender = null;
          >> >> QueueSession aSession = null;
          >> >> QueueConnection aConnection = null;
          >> >> try {
          >> >> Properties p = new Properties();
          >> >>
          >> >p.load(JMSProperties.class.getResourceAsStream("jms.properties"));
          >> >> InitialContext aIC = new InitialContext(p);
          >> >> QueueConnectionFactory aFactory = (QueueConnectionFactory)
          >> >aIC.lookup(
          >> >> p.getProperty("queue.connection.factory.name")
          >> >> );
          >> >> aConnection = aFactory.createQueueConnection();
          >> >> aConnection.start();
          >> >> aSession = aConnection.createQueueSession(
          >> >> false,
          >> >> QueueSession.AUTO_ACKNOWLEDGE
          >> >> );
          >> >> Queue aQueue = (Queue) aIC.lookup(args[0].trim());
          >> >> aSender = aSession.createSender(aQueue);
          >> >>
          >> >> int i = 0;
          >> >> for (; i < 20; i++) {
          >> >> sendMessage(aSender, aSession, i);
          >> >> }
          >> >> } catch (Exception e) {
          >> >> e.printStackTrace();
          >> >> } finally {
          >> >> try {
          >> >> if (aSender != null) {
          >> >> aSender.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aSession != null) {
          >> >> aSession.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aConnection != null) {
          >> >> aConnection.stop();
          >> >> aConnection.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> }
          >> >> }
          >> >> }
          >> >>
          >> >> Here is the server program:
          >> >> package com.malani.jms.transaction;
          >> >>
          >> >> import java.util.*;
          >> >>
          >> >> import javax.jms.*;
          >> >> import javax.naming.*;
          >> >>
          >> >> import com.malani.jms.resources.*;
          >> >>
          >> >> public class Server {
          >> >> public static final String JNDI_QUEUE_NAME =
          >> >"transaction_queue_jndi_name";
          >> >>
          >> >> public static void main(String[] args) {
          >> >> QueueReceiver aReceiver = null;
          >> >> QueueSession aSession = null;
          >> >> QueueConnection aConnection = null;
          >> >> try {
          >> >> Properties p = new Properties();
          >> >>
          >> >p.load(JMSProperties.class.getResourceAsStream("jms.properties"));
          >> >> InitialContext aIC = new InitialContext(p);
          >> >> QueueConnectionFactory aFactory = (QueueConnectionFactory)
          >> >aIC.lookup(
          >> >> p.getProperty("queue.connection.factory.name")
          >> >> );
          >> >> aConnection = aFactory.createQueueConnection();
          >> >> aConnection.start();
          >> >> aSession = aConnection.createQueueSession(
          >> >> true,
          >> >> -1 // doesn't really matter
          >> >> );
          >> >> Queue aQueue = (Queue) aIC.lookup(JNDI_QUEUE_NAME);
          >> >> aReceiver = aSession.createReceiver(aQueue);
          >> >> final QueueSession aQS = aSession;
          >> >> MessageListener aML = new MessageListener() {
          >> >> public void onMessage(Message m) {
          >> >> try {
          >> >> TextMessage aTM = (TextMessage) m;
          >> >> String s = aTM.getText();
          >> >> System.out.println("Text is:\t" + s);
          >> >> int i = Integer.parseInt(s);
          >> >> if (i < 15) {
          >> >> aQS.commit();
          >> >> } else {
          >> >> aQS.rollback();
          >> >> }
          >> >> } catch (JMSException e) {
          >> >> e.printStackTrace();
          >> >> }
          >> >> }
          >> >> };
          >> >> aReceiver.setMessageListener(aML);
          >> >> byte[] b = new byte[1];
          >> >> System.in.read(b);
          >> >> } catch (Exception e) {
          >> >> e.printStackTrace();
          >> >> } finally {
          >> >> try {
          >> >> if (aReceiver != null) {
          >> >> aReceiver.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aSession != null) {
          >> >> aSession.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> try {
          >> >> if (aConnection != null) {
          >> >> aConnection.stop();
          >> >> aConnection.close();
          >> >> }
          >> >> } catch (JMSException e) {}
          >> >> }
          >> >> }
          >> >> }
          >> >>
          >> >> Here is the properties file:
          >> >> #
          >> >> java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
          >> >> java.naming.provider.url=t3://localhost:7001
          >> >> queue.connection.factory.name=weblogic.jms.ConnectionFactory
          >> >>
          >> >#queue.connection.factory.name=weblogic.jms.MessageDrivenBeanConnectionFacto
          >> >ry
          >> >> #queue.connection.factory.name=transaction_connection_factory_jndi_name
          >> >>
          >> >> Here is the JMSProperties file:
          >> >> package com.malani.jms.resources;
          >> >>
          >> >> public class JMSProperties {
          >> >> }
          >> >>
          >> >> The first time the server is run, it hangs at 16. Messages 17, 18,
          >and
          >> >19
          >> >are
          >> >> not processed. Is this correct behavior:
          >> >> Text is: 0
          >> >>
          >> >> Text is: 1
          >> >>
          >> >> Text is: 2
          >> >>
          >> >> Text is: 3
          >> >>
          >> >> Text is: 4
          >> >>
          >> >> Text is: 5
          >> >>
          >> >> Text is: 6
          >> >>
          >> >> Text is: 7
          >> >>
          >> >> Text is: 8
          >> >>
          >> >> Text is: 9
          >> >>
          >> >> Text is: 10
          >> >>
          >> >> Text is: 11
          >> >>
          >> >> Text is: 12
          >> >>
          >> >> Text is: 13
          >> >>
          >> >> Text is: 14
          >> >>
          >> >> Text is: 15
          >> >>
          >> >> Text is: 16
          >> >>
          >> >>
          >> >> What happened to message 17, 18, and 19?
          >> >>
          >> >> Now, if I stop the server, and start it again, I see the requequing
          >and
          >> >redelivery
          >> >> of the messages as shown below:
          >> >> Text is: 15
          >> >>
          >> >> Text is: 16
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >> Text is: 15
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 16
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >> Text is: 15
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 16
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >> Text is: 17
          >> >>
          >> >> Text is: 18
          >> >>
          >> >> Text is: 19
          >> >>
          >> >>
          >> >> Is there some optimization going on?
          >> >>
          >> >> Thank you so much....
          >> >>
          >> >>
          >> >
          >> >
          >

JMS timeout

I have read quite a bit on these groups about JMS and session beans,
          but I still haven't found an answer. Let me explain my problem:
          First off I am using Weblogic 5.x
          I have a stateless session bean that, amongst other things, calls
          a method on an external class which is repsonsible for sending a JMS
          message. This external class sets up the JMS connection, session,
          queue, etc.. The problem is, the receiver always times out when it
          tries to receive a message. Can this be avoided? I have moved the
          call to the method outside the UserTransaction (I would prefer it to
          be inside), and tried transacted and non transacted JMS sessions. Is
          there anyway to not have the JMS timeout while inside an EJB? Any
          information would be greatly appreciated. Thanks.
          Tomato


Is there no chance you can change your architecture
to use a MessageListener?
Unfortunately thats not an option any more.
I've always found JMS to be attrocious when it comes
to synchronous messaging - guarranteeing you will
receive a message within a certain time-frame is
pretty much impossible.In that case would putting a loop be helpful, specially to avoid queues being locked?

Database connection timeouts and datasource errors

Connections in the pool randomly die overnight. Stack traces show that for some reason, the evermind driver is being used even though the MySql connection pool is specified.
Also, the evermind connection pool is saying connections aren't being closed, and the stack trace shows they're being allocated by entity beans that are definitely not left hanging around.
Sometimes we get non-serializable errors when trying to retrieve the datasource (this is only after the other errors start). Some connections returned from the pool are still good, so the application limps along.
EJBs and DAOs both use jdbc/SQLServerDSCore.
Has anyone seen this problem?
<data-sources>
     <data-source
          class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource"
          name="SQLServerDSCore"
          location="jdbc/SQLServerDSCore"
          xa-location="jdbc/xa/SQLServerXACore"
          ejb-location="jdbc/SQLServerDSCore"
          connection-driver="com.mysql.jdbc.Driver"
          min-connections="5"
          username="xxx"
          password="xxx"
          staleness-timeout="3600"
          alive-poll-query="SELECT 1 FROM medispan"
          url="jdbc:mysql://1.2.3.4:3306/dbo?autoReconnect=true&autoReconnectForPools=true&cachePrepStmts=true&is-connection-validation-required=true"
          inactivity-timeout="30"
     >
          <property name="autoReconnect" value="true"/>
          <property name="autoReconnectForPools" value="true"/>
          <property name="is-connection-validation-required" value="true"/>
          <property name="cachePrepStmts" value="true"/>
     </data-source>
</data-sources>

Rick,
OC4J 9.0.4.0.0 - BTW, do you know of any patches?As far as I know, there are no patches for the 9.0.4
production version of OC4J stand-alone.
I'm using container managed persistence,It was not clear to me, from your previous post, that you
are using CMP entity beans.
I found staleness-timeout and alive-poll-query
somewhere on a website when trying to track this
down. Here's four sources:Those sources refer to OrionServer -- and an older version, too, it seems.
Like all other Oracle products that start out as somebody
else's -- including, for example, JBuilder (that became "JDeveloper"), Apache Web Server (that became "Oracle HTTP Server") and TopLink -- their development paths diverge, until, eventually, there is absolutely no similarity between them at all. Hence, the latest versions of OC4J and "OrionServer" are so different, that you cannot be sure that something that works for "OrionServer" will work for OC4J.
I recall reading something, somewhere, sometime about configuring OC4J to use different databases (other than Oracle), but I really don't remember any details (since it was not relevant to me, because we only use Oracle database). In any case, it is possible to use a non-Oracle database with OC4J.
Good Luck,
Avi.

Traceroute timeouts and lots of packet loss when a...

I host various site via the above, and since late last night and today, I am having connection timeout issues on all of them (but sites like bbc, bt etc are fine). I contacted them and performed a traceroute to my default site southee.co.uk which timed out. Below are the results:
traceroute to southee.co.uk (37.61.236.12), 64 hops max, 52 byte packets
1 bthomehub (192.168.1.254) 2.733 ms 2.414 ms 2.415 ms
2 esr5.manchester5.broadband.bt.net (217.47.67.144) 72.412 ms 29.705 ms 131.735 ms
3 217.47.67.13 (217.47.67.13) 31.390 ms 29.680 ms 103.936 ms
4 213.1.69.226 (213.1.69.226) 41.172 ms 32.700 ms 129.323 ms
5 31.55.165.103 (31.55.165.103) 30.791 ms 31.639 ms 130.306 ms
6 213.120.162.69 (213.120.162.69) 31.248 ms 59.138 ms 30.657 ms
7 31.55.165.109 (31.55.165.109) 32.159 ms 31.507 ms 31.513 ms
8 acc2-10gige-9-2-0.mr.21cn-ipp.bt.net (109.159.250.228) 31.499 ms 31.325 ms
acc2-10gige-0-2-0.mr.21cn-ipp.bt.net (109.159.250.194) 31.197 ms
9 core2-te0-12-0-1.ealing.ukcore.bt.net (109.159.250.147) 41.744 ms
core2-te0-13-0-0.ealing.ukcore.bt.net (109.159.250.139) 41.346 ms
core2-te0-5-0-1.ealing.ukcore.bt.net (109.159.250.145) 41.744 ms
10 peer1-xe3-3-1.telehouse.ukcore.bt.net (109.159.254.211) 39.527 ms
peer1-xe10-0-0.telehouse.ukcore.bt.net (109.159.254.122) 38.791 ms 38.910 ms
11 te2-3.sov-edge1.uk.timico.net (195.66.224.111) 54.032 ms 37.941 ms 38.642 ms
12 78-25-201-30.static.dsl.as8607.net (78.25.201.30) 45.830 ms 46.413 ms 42.448 ms
13 * * *
They then performed a traceroute from the server and got the following, again with timeouts and packet loss. See below:
1. 37.61.236.1 0.0% 10 0.5 0.7 0.4 2.9 0.8
2. ae0-2061.ndc-core1.uk.timico 0.0% 10 0.3 0.3 0.2 0.5 0.1
3. te2-3.sov-edge1.uk.timico.ne 0.0% 10 10.5 9.7 4.2 30.2 8.7
4. linx1.ukcore.bt.net 0.0% 10 4.1 4.3 4.1 5.9 0.6
5. host213-121-193-153.ukcore.b 0.0% 10 5.5 8.0 4.9 12.7 2.3
6. acc2-10GigE-4-3-1.mr.21cn-ip 0.0% 10 11.4 11.4 11.4 11.6 0.1
7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8. 31.55.165.108 0.0% 10 12.1 12.1 11.8 12.4 0.2
9. 213.120.162.68 0.0% 10 12.0 12.1 12.0 12.3 0.1
10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
I've just spent a fustrating 15 minutes with Bt Support chat who just seemed want to pass me on to the BT Business team, so I thought I'd post here, for a more informed response.

Hi Jane, Thanks for the reply. I have now purchased an AEBS(n) to try to overcome this problem. The Apple site says it is compatible with all versions of Airport card so I thought it would solve the problem. My new problem is to be found here: http://discussions.apple.com/thread.jspa?threadID=1087292&tstart=0
However to answer your questions, The OS is 10.4.10 and I have run every updater I can find for all Macs concerned. hope this helps.

Re: timeouts and ExternalConnection

Tim,
Use a Timer class of Framework library to have an explicit control over
the connection. If the end-of-stream marker is not received within a
specified interval of time, handle the situation.
ExternalConnection class does not have any timeout feature of its own,
but it would be a good idea to have one in future.
Braja.
\\\|///
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~oOOo- (_) -oOOo~~~~~~~
BRAJA KISHORE CHATTARAJ
Consultant, Analysts International Corporation.
Work : Sphinx Pharmaceuticals (A division of Eli Lilly & Co.)
(919) 419-5798
Home : 1801, Williamsburg Rd., #41H, Durham, NC 27707.
(919) 403-7296
E-mail : [email protected]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Oooo~~~~~~~
oooO ( )
Please respond to Tim Kannenberg <[email protected]>
Subject: timeouts and ExternalConnection
I am working on a Forte service that uses a socket listener (implemented
using the ExternalConnection class) to handle incoming messages. The
messages vary in length, so the code for processing each connection
loops until it finds an end-of-stream marker. If some client is
erroneously sending messages without the marker, it'll loop forever. I
would like the connection to time out if it doesn't receive any valid
messages within a fixed length of time. Is there some functionality
I've overlooked in ExternalConnection that would handle this? If not,
does anybody have an example of a good way to implement it?
Thanks in advance,
Tim
Tim Kannenberg
Strong Capital Management
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

I've re-run the speed test. Here they are. Download speedachieved during the test was - 19915 Kbps For your connection, the acceptable range of speedsis 12000-29036 Kbps . Additional Information: IP Profile for your line is -29036 Kbps Upload speed achieved during the test was - 3819 Kbps Additional Information: Upstream Rate IP profile on your line is - 10000 Kbps Although the speed has dropped markedly since Saturday, its the dropouts, the VPN unable to connect and the slow respnses when trying to connect to websites quickly (DNS issue?) that is bothering me. It's not just one website that the problem is with, its any.

Frequent timeouts and poor performance

Hello,
Starting this morning I'm experiencing a lot of timeouts and performance issues with my SQL Azure DB (located in West US), causing several Azure hosted services to fail. I've checked everything I can think of and it nothing shows a clear problem with our
databases. I'm not seeing anything on the dashboard, but can't help but wonder if there is an issue going on that hasn't been detected.
Any suggestions on how to troubleshoot this issue?
Thanks,
-Fabio

Hi Fabio,
I work on the Cotega monitoring service for SQL Azure and I can also confirm that we saw a few customer who we notified of performance issues with SQL Azure as well.
Now that I write this, I am wondering if it might be worth adding to the service a page that lets anyone see the historical performance of SQL Azure based on aggregated data from all of the customers databases that we currently monitor. I wonder if
that would be useful for situations like this?

SQL Timeouts and Blocking Locks

SQL Timeouts and Blocking Locks
Just wanted to check in and see if anyone here has feedback on application settings, ColdFusion settings, JBOSS settings or other settings that could help to limit or remove SQL Timeouts and blocking locks on SID's.
We're using MS SQL 2000 with JBOSS and IIS5.
We've been seeing the following error in our logs that starts blocking locks in SQL:
java.sql.SQLException: [newScale] [SQLServer JDBC Drive] [SQLServer] Lock request time out period exceeded.
Once this happens, we're hosed until we remove the blocking SID in SQL. These are the connections to the application.
Any feedback would be great. Thanks!

Hi
This is your exact solution:
Select a.username, a.sid, a.serial#, b.id1, c.sql_text
From v$session a, v$lock b, v$sqltext c
Where b.id1 in( Select distinct e.id1
from v$session d , v$lock e
where d.lockwait = e.kaddr ) and
a.sid = b.sid and
c.hash_value = a.sql_hash_value and
b.request =0;
Thanks
Sarju
Oracle DBA
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by I'm clueless:
Can someone give me the SQL statement to
show if there are any blocking database locks and if so - which user is locking the Database?
Thanks in Advance<HR></BLOCKQUOTE>
null

Session timeout and custom sso

Hi,
can anyone tell me how the session and idle timeout feature in Apex exactly works?
I built several applications in a workspace and do a sso authorization by setting a common cookie name. In addition to that i set the values for session length and idle timeout and assumed that the session length would be synchronized over all applications. But this doesn't seem to work. For instance, i set the idle timeout to 10 minutes in all applications and now i work for 15 minutes continously in application A and after that i switch over to application B (using the same session id!), the session is already expired in B.
Is this behavior correct? And, if yes, how can i set up a synchronization over all applications?
Jens

Anyone?

Is there a risk of setting a console connection timeout and what is the recommended setting?

Is there a risk of setting a console connection timeout and what is the recommended setting? Please suggest if there is any best prctice documentation that can be referred.

Hi Henrik
depend on what you need or what your security policy says for my lab gear i use 60 minutes. because i know how can access this. if you have gear outside in insecure space set it to a minimum or disable the console. everybody how can access your gear can break in. simple restart and boot w/o config. and you are in.
it realy depends how secure is your space and how much security you need.
and than the settings for policy have to match, what sec do you have if your console login and logout is secure. but when you restart you can simple break in by starting w/o config and than load it.
HTH
Patrick

Using MySQL DB on Weblogic 10.3.2 for JMS Store and etc.

Hi,
I am planning to use MySQL DB w Weblogic 10.3.2 server.
I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
Can anyone please help me understand any serious issues or considerations of this combination?
Thanks
Sagar

Hi,
I am planning to use MySQL DB w Weblogic 10.3.2 server.
I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
Can anyone please help me understand any serious issues or considerations of this combination?
Thanks
Sagar

What is the difference between Session timeout and Short Session timeout Under Excel Service Application -- session management?

Under Excel Service Application --> session management; what is the difference between Session timeout and Short Session timeout?

Any call made from the API will automatically be set to the “Session Timeout” period, no matter
what. Calls made from EWA (Excel Web Access) will get the “Short Session Timeout” period assigned to it initially.
Short Session Timeout and Session Timeout in Excel Services
Short Session Timeout and Session Timeout in Excel Services - Part 2
Sessions and session time-outs in Excel Services
above links are from old version but still applies to all.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

BPEL - Handling invocation timeouts and Modifying Partner Link endpoints

Hi,
We've built the basic functionality that we need in our BPEL process but are facing 2 specific questions that we are a bit stuck with and would really appreciate some help on..
1. Our BPEL process calls an external synchronous web service. We have a requirement that if this external web service is unable to respond to our BPEL process within a fixed timespan (say 1 minute), we need to treat this as a timeout and move on. Can anyone suggest what settings are required for this?
2. The second query is with regards to a likely situation we will face after go-live. If the URL of the external service changes (lets say the service moves from one server to another), ideally we would want to be able to configure this URL change rather than have to modify the WSDL and rebuild the BPEL project in JDev with the new WSDL. Does the BPEL Admin Console provide any such feature? As far as I can recall from a project a couple of years ago, Websphere Process Server did provide such a feature and I'm looking for something similar here but have not found it yet. I am not looking to use dynamic endpoints within our flow - just for an admin feature that would allow me to modify the URL externally via the console.
Would really appreciate any suggestions on these 2 points..
Thanks and Regards,
TB

In response to your second query -
a) you don't need to rebuild the BPEL project in Jdev in order to change the wsdl file. If you update the WSDL file with new values for your endpoint simply clear the WSDL cache and the process will pick up the new values in the new instances created from thereon.
b) or if you dont' want to update the wsdl manually, you can write a piece of java code to change the endpoint URL's for the deployed BPEL processes using the code given here
hth

Azure Scheduler Job Timeouts and Retries?

We have a WEBAPI running outside of Azure and want to schedule one of the methods with Azure. It loads data from SharePoint Online into an SQL database on-Prem. It can take 15 minutes to complete. I'm doing a GET call to the URI, but
it reports it's FAILED timing out and retrying... from our SQL logs the job appears to complete, though not clear if it ran multiple times. Any way to fix this? No way to adjust timeout and retries in Azure job Scheduler?

Hi,
It looks like you are using the Azure Scheduler service, not the Azure Automation service. Is that correct? This forum is only for the Azure Automation service.
If so, I will move this thread to the Scheduler forum.

Session timeout and Custon login module

Hi,
Dev Platform: Jdev 10.1.3.4.0, Oracle 10.2.4
I'm trying to trap the session timeout and display a page. I'm using the code below from Frank Nimphius. I've also provided a console log of what is happening when the application times out. Instead of the filter being called the system is calling the dblogin module and attempting to login the anonymous user. I renamed the anonymous user and I just see log entries where the system attempted to find the anonymous user.
If I use the application to logout I get a Logout page with a button to confirm the logout. When I press the button the session is invalidated and the filter code brings up my "Session Timeout" notification page. This isn't what will happen in the end but I just wanted to tell you that the filter does work in certain instances.
How can I make the system not attempt to login the anonymous user and have the filter code run?
TIA, Dave
package isdbs.view.security;
import java.io.IOException;
import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class ApplicationSessionExpiryFilter implements Filter {
    private FilterConfig _filterConfig = null;
    public void init(FilterConfig filterConfig) throws ServletException {
        _filterConfig = filterConfig;
    public void destroy() {
        _filterConfig = null;
    public void doFilter(ServletRequest request, ServletResponse response,
                         FilterChain chain) throws IOException, ServletException {
        String requestedSession =   ((HttpServletRequest)request).getRequestedSessionId();
        String currentWebSession = ((HttpServletRequest)request).getSession().getId();
        boolean sessionOk = currentWebSession.equalsIgnoreCase(requestedSession);
        // if the requested session is null then this is the first application
        // request and "false" is acceptable
        if (!sessionOk && requestedSession != null){
            // the session has expired or renewed. Redirect request
            ((HttpServletResponse) response).sendRedirect(_filterConfig.getInitParameter("SessionTimeoutRedirect"));
        else{
            chain.doFilter(request, response);
}Mar 30, 2009 9:38:04 AM oracle.security.jazn.oc4j.RealmUserAdaptor isMemberOf
FINE: JAAS-OC4J: Membership check for group: ISDBS_USER failed for user: anonymous
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option debug = true
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option log level = log all
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option logger class = null
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option data_source_name = jdbc/elearnDS
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option user table = TBL_LOGIN
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option roles table = XREF_LOGIN_ROLE
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option username column = LOGIN_NM
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option password column = PASSWORD
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option roles column = ROLE_NM
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option user pk column = LOGIN_NM
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option roles fk column = LOGIN_NM
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option password encoding class = oracle.sample.dbloginmodule.util.DBLoginModuleClearTextEncoder
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option realm_column = null
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] option application_realm = null
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] login called on DBTableLoginModule
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] Calling callbackhandler ...
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] Username returned by callback = null
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] User query string: select LOGIN_NM,PASSWORD, LOGIN_ATTEMPTS, ACTIVE_IND from TBL_LOGIN where lower(LOGIN_NM)= lower((?))
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] Logon Successful = false
09/03/30 09:38:04 [DBTableOraDatasourceLoginModule] Abort called on LoginModule
Mar 30, 2009 9:38:04 AM oracle.security.jazn.oc4j.OC4JUtil doJAASLogin
WARNING: Login Failure: all modules ignored
javax.security.auth.login.LoginException: Login Failure: all modules ignored
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:921)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at oracle.security.jazn.oc4j.OC4JUtil.doJAASLogin(OC4JUtil.java:241)
     at oracle.security.jazn.oc4j.GenericUser$1.run(JAZNUserManager.java:818)
     at oracle.security.jazn.oc4j.OC4JUtil.doWithJAZNClsLdr(OC4JUtil.java:173)
     at oracle.security.jazn.oc4j.GenericUser.authenticate(JAZNUserManager.java:814)
     at oracle.security.jazn.oc4j.FilterUser.authenticate(JAZNUserManager.java:1143)
     at com.evermind.server.http.EvermindHttpServletRequest.checkAndSetRemoteUser(EvermindHttpServletRequest.java:3760)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:706)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Mar 30, 2009 9:38:04 AM oracle.security.jazn.oc4j.GenericUser authenticate
FINE: JAAS-OC4J: Authentication failure for user: null
Mar 30, 2009 9:38:04 AM oracle.security.jazn.oc4j.RealmUserAdaptor isMemberOf
FINE: JAAS-OC4J: Membership check for group: ISDBS_USER failed for user: anonymous

I added an HttpSessionListener upon login here's what I get:
09/03/31 08:21:25 Inside sessionCreated
09/03/31 08:21:25 Before New session createb = 0
09/03/31 08:21:25 Created session id: 854b4b95cf28ceb065d0489a31ee79c19feabb80716f6d828b77fc7044b210bf
09/03/31 08:21:25 After New session count = 1
At session timeout here's what I get:
09/03/31 08:23:27 Count before destroyed = 1
09/03/31 08:23:27 Destroyed session id: 854b4b95cf28ceb065d0489a31ee79c19feabb80716f6d828b77fc7044b210bf
09/03/31 08:23:27 Count after destroyed = 0
09/03/31 08:23:27 Inside sessionCreated
09/03/31 08:23:27 Before New session createb = 0
09/03/31 08:23:27 Created session id: 854b4b95cf28ceb065d0489a31ee79c19feabb80716f6d828b77fc7044b210bf
09/03/31 08:23:27 After New session count = 1
Notice that the session Id in each case is IDENTICAL. That is why the Filter code isn't doing what it is intended to do. Whay is the same session ID being created after it is destroyed? Is there a configuration parameter that controls it?
Thanks,
Dave

JMS timeout and redelivery

Similar Messages

Maybe you are looking for