JMS J2EE question

I am using 6.40, and am running JMS queue tests.
The J2EE engine dies frequently, I have to re-install about once a day.
However, I have consistently increased the size of the Data Volume when I install, and as I do this, the time between crashes increased from about 1 day to every 2 to three days. Now I only have to re-install about every 2 to 3 days.
I guess that means I am filling up the data logs or something. The default is about 400 MG, and I have currently set it to 9000 mg and am getting better response. IN fact I am not sure I will have to reinstall this latest implementation, the 9000 mg install seems to be hanging in there so far.
By the way, the crash behavior is that the broker will not accept send or receive JMS messages, and the J2EE engine will not come up, even if I restart the SAP System from the MMC.
Is there any way to periodically flush the data volume or the logs so it will never crash ?
Is there any way to do this in an automated manner?
Thanks, John

Hi John,
You should enable the "overwrite" mode for the log area. Open the Database Manager, go to Configuration -> Log Settings and choose the Overwrite Mode for the Log Area option.
Hope that helps!
Vladimir

Similar Messages

Problem with Sender JMS J2EE adapter...

I have configured the sender JMS J2EE adpater. I am getting this error at Adapter monitoring:
<b>Sender channel. Details: Last Exception during send at Fri May 25 09:44:18 CEST 2007: Error converting Message: 'java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 1: missing structure(s) in last recordset'.</b>
I am using recordset structure as Header,1,Item,99999. and also i am ignoring the recordsetName...i tried confiuring the File adapter using same parameters as in JMS adapter it is not giving any error at Adapter Monitoring.
Also i configured File adapter by putting in their the parameters of J2EE JMS adapter in Module tab, it too worked...
so What is exactly this error, if anyone can please tell me...

Hi,
Check some links for FCC
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
File Receiver with Content Conversion
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
File Receiver with Content Conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani

Problem in Sender JMS J2EE adapter....

Hello All.
I have configured the sender JMS J2EE adpater. I am getting this error at Adapter monitoring:
<b>Sender channel. Details: Last Exception during send at Fri May 25 09:44:18 CEST 2007: Error converting Message: 'java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 1: missing structure(s) in last recordset'.</b>
I am using recordset structure as Header,1,Item,99999. and also i am ignoring the recordsetName...i tried confiuring the File adapter using same parameters as in JMS adapter it is not giving any error at Adapter Monitoring.
Also i configured File adapter by putting in their the parameters of J2EE JMS adapter in Module tab, it too worked...
so What is exactly this error, if anyone can please tell me...
Thnsk in Advace

> I think you have to figure out first, which codepage you really have, not just try. Maybe you ask someone or you check with a hex editor.
Hi Stefan,
Finally we solved the problem.
As you said above to figure the the codepage, we asked to our MQ team for the same and found that they are using ISO-8859-1. In XI we were also trying with multiple conbinations (ISO-8859-1, UTF-8 and many more), but didn't get any success.
Finally MQ team changed their encoding to UTF-8 and in XI we used ISO-8859-1 and we get the success in picking the data with spl char. Even though in XI the spl char comes in destorted order but at the receiver end they are in proper shape.
Thanks a lot for your help.
Regards,
Sarvesh

JMS queue question

Hi all,
I am using Weblogic Application Server and say I have 1000 messages in a JMS Queue say "Q1".
Q1. How are these messages picked up from the queues? i.e. by a thread etc.
Q2. If they are picked up by threads then who configures these threads? Are they default threads created by the Weblogic Application Server or are user-created threads?
Q3. Also, if 20 threads are involved in picking the messages from the queue and of them one thread snaps while picking the message then what will happen? and what will be the solution??
Thanks.

Q1/Q2*:
The answer to your question is "its provider specific".
You will need someone who explicitly works on weblogic to provide specifics so you may want to utilize a weblogic specific forum instead of a generic JMS forum
I'll try to answer this in very generic terms that should apply to all providers:
If you are receiving messages with an MDB: there is a thread pool associated with the resource adapter which plugs the JMS provider into the server. This is generally configured as part of the application server configuration. That pool dictates the maximum number of threads which can call the same MDB's at the same time.
If you are receiving messages with a Servlet: In this case, you are probably calling receive within the servlet. That will use the thread provide by the webstack which is executing the servlet
If you are receiving messages in an AppClient or Standalone provider: You are using your own thread if you call receive(), or a thread provided by the provider if you are calling onMessage()
In all cases, the provider may be allocating additional threads "beneath the covers" to process those messages.
Q3*:
I'm not quite sure what snaps means. Threads run until they exit. I'm going to guess that the question is "what if the MDB or code throws a RuntimeException". If you mean something different, please supply a more specific description of the error.
This one depends on what whether or not you are using transactions and how you are receiving those messages.
If you are using transactions in an MDB: the transaction will rollback and the message will be redelivered to another consumer.
In all other cases, it depends on the specifics (I was going to list them but it seems like to much work for a Friday afternoon).
If you are using a non-transacted or non-MDB method to retrieve the messages, let me know and I can tell you how, per the JMS and J2EE specs, it should work. I'll need to know acknowledge mode/transaction, type of client and if you are calling receive() or onMessage().
-- Linda

Pointer to an unanswered j2ee question

This is just a pointer to a question posted on j2ee that remains unanswered; hopefully someone here can help - I'm attempting to get into j2ee stuff, obviously.
Regards,
Here's the post: http://forum.java.sun.com/thread.jspa?threadID=5305753&tstart=0
~Bill
Edited by: abillconsl on Jun 17, 2008 1:22 PM

Two books:
(1) "Database Modeling and Design" by Toby Teorey,
(2) "Patterns of Enterprise Application Architecture" by Martin Fowler.
You'll want to know about SQL and normalization. The Teorey book is good for both. Fowler's book will help with writing that data access layer in Java. - MOD

Small weblogic.jar for jms/j2ee clients of weblogic

          We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          I attempted to use the whitepaper document distributed by BEA for creating a smaller
          jar file, but it did not work. Has anyone else in the user community successfully
          created the jar file and if so could they give me some insight on how they did
          it.
          Thanks,
          Ashish


Hi Ashish,
          I've personally used the "URL" class loader option with success,
          and I know that several customers have also used this option, as
          well as the other options for years. Feel free to
          post more detail than "it did not work", and I may be able
          to help you out.
          Tom, BEA
          P.S. If 8.1 is an option, you may with to consider using the
          thin client jars it supplies.
          Ashish Bisarya wrote:
          > We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          > to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          > I attempted to use the whitepaper document distributed by BEA for creating a smaller
          > jar file, but it did not work. Has anyone else in the user community successfully
          > created the jar file and if so could they give me some insight on how they did
          > it.
          >
          > Thanks,
          > Ashish

JMS - Use question

Hey Folks,
Just reading a book on JMS for the first time and i just have a few philosophical questions on the use of it. In the book it gives me an example of setting up a JMS queue and then using a MDB to receive a message and then does a credit check on a customer!!
So after one has gone through all the hassle of configuring your factories,setting up your queue, creating your MDB and then configuring it your are finally ready to write code to do your business requirements!!
Now my first thought were, why would i do all that work just to do a credit check on a customer asynchronously, if i was using plain old POJO�s , why wouldnt i just spin off a thread to do this for me in the backround instead of having to do all the above?? So what am i missing here??
Next point that i need some clarity on is more related to a production setup. Say i have 10 nodes, does one just create one JMS channel that all 10 nodes use or do they each have a channel for every node?? If they have a channel for every node then why would i use JMS?? Ok loose coupling, great but i can get that if i create my own observer pattern, what extra will it give me than a normal observer pattern?? I assume in the above scenario that you have no external applications listening, so everything that needs to listen for the message is in your JVM!! I understand if you have SAP or any other external applications listening
Last but not least, is it fair to make a comparison JMS to tibco messaging bus?? If so why, if not why?? ;)
Thanks for any help on the matter, like i said im just reading up on it now and need a few thoughts cleared up!!
Cheers,
LL

> So when you say chained, i take it you can set the
order in which you want your beans to be called
first(assuming in a topic scenario where you have
several listeners)?? is that possible with JMS?? if
so how??
We've written a custom Process Manager that receives messages and uses XPath and XSL to coordinate several JMS applications (all of our messages are XML). We typically don't use topics because we don't want multiple applications getting the same message. Each application does its work in turn, not at the same time.
> Yeh i can see how it would work in this scenario but
you still have other options to solve this problem
without the need of JMS!!
There's always more than one way to solve a problem.
> i suppose im looking for a scenario where i would say
to myself, yes thats a job for JMS!! And in this
scenario exclude the need to talk to external
applications!!
I wouldn't want to design a large system with multiple teams working on multiple applications, each with its own processing needs without JMS. Tuning is pretty easy. Adding more horsepower at any point in the chain is pretty easy.
But it may be that I just reach for the tools that I am most familiar with.
Dwayne

J2ee Questions

Hi;
I have same questions concerning J2ee platform :
Q1: I have of the performance problem with EJB entity and would like to use mapping Objects/Tables => so its a good solution or not ? which tool I must to use ?
Q2: how realized a identification of users with diffirents profils (the better solution ?).
Q3: which is your opinion on struts plateform (performance, complexity, ...).
Best regards

Hi;
I'am sorry I have implemented CMP 2.0 EJB under Websphere 5.0 and its very catastrophic for the performance because I manage a big database on DB2.
I have realized of the performance tests with a architecture Mapping objects/Tables (JDO) and its better.
Q2: I will realize a web application (Intranet) and my question : JAAS its a good solution for the indentification or there are another solution ?
Regards;

J2EE questions with thick client

I�m trying to move from an existing client-server Swing application (currently talks directly to a database via JDBC) to a 3-tier J2EE model. This is primarily so that I can use HTTP web services on port 80 to bypass firewalls, and to allow for future architectural expansion beyond the current Swing client. I am experienced with Java and Swing, but very new to J2EE, so I'm hoping that there are some obvious points that I am missing.
I am surprised by the lack of 'thick client' examples, tutorials, and documentation that I see with J2EE - almost everything is oriented towards HTML web applications. Here are some questions that I have for using J2EE with a thick client (specifically Swing):
* Where are business logic methods executed? On the client or the server? I get the impression that with J2EE and EJB, all business logic is executed on the server via RPC. Can I choose to have this done in the client instead? If so, how?
* My Swing applications depend heavily on PropertyChangeEvents being fired from the data objects in order for me to update my UI. If the answer to the previous question is that all business logic is executed on the server, then is there a way for my client listeners to receive these change events? If not, how do I know when to update my UI?
* If all business methods are executed on the server, what about accessor methods? Do those need to make a round trip for every call? I've read a little bit about Data Transfer Objects (DTO's) to solve this, but I don't completely understand the concept - if DTO's have no embedded business logic, then how do I know whether a particular getXXX() method has business logic attached to it, and therefore whether to reference the DTO or the server EJB object?
Thanks for answers to these questions. Googling for 'J2EE' and 'thick client' came up with no useful information; I'm hoping to post a HOWTO that will help others after I get this running.

The petstore sample application from blueprints (java.sun.com/blueprints) has an admin module which is a Java Webstart enabled "thick client" that gets business logic processing done on the server. Also the client chapter for the "designing enterprise apps with J2EE" book (also available as html from the same link) gives some tips on designing clients. These may be of help to you

JMS Transaction Questions

          Greetings,
          I have the following questions regarding Transactions in JMS:
          1. What constitutes a transaction in JMS? Assuming there are 2 clients, one which
          is just a Subscriber and the other just a Publisher. What will constitute a transaction
          in this scenario?
          2. While configuring, JMS Connection Factory, a parameter present is " Transaction
          Timeout ", with a defualt value of 3600 secs. At what point, does this time starts
          ticking ? Is there anyway to disable this value or the only solution is to increase
          it as required.


          vinay s wrote:
          > Greetings,
          >
          > I have the following questions regarding Transactions in JMS:
          > 1. What constitutes a transaction in JMS? Assuming there are 2 clients, one which
          > is just a Subscriber and the other just a Publisher. What will constitute a transaction
          > in this scenario?
          >
          A receive or send operation performed under a transaction. The operation
          becomes transactional.
          >
          > 2. While configuring, JMS Connection Factory, a parameter present is " Transaction
          > Timeout ", with a defualt value of 3600 secs. At what point, does this time starts
          > ticking ? Is there anyway to disable this value or the only solution is to increase
          > it as required.
          This applies to transacted sessions. A special kind of transactional behavior
          unique to JMS. WL JMS also supports user transactions (JTA), which
          is more unique.
          Note that 3600 seconds is a long time, standard transactions actually
          default to a limit of 30 seconds...
          To learn about this stuff, I recommend reading the WebLogic JMS Programmer's guide - there
          is a chapter on
          transactions. Check out the performance white-paper I posted to this newsgroup last
          Thursday - there is
          a section in there on transacted sessions vs. user transactions...

Tomcat , JMS & J2ee RI

anyone here knows if there is a way to configure Tomcat to support JMS on servlets by using the J2ee Reference Implementation Server as the JMS provider? I know there is openjms and other jakarta components that can help tomcat do jms, but is there a way to do it with the j2ee ri?

Both The tomcat.jar and j2ee.jar implements apache.* classes, and they are conflicting with each other. If you add "j2ee.jar" to Tomcat's classpath, you'll get an error message trying to start Tomcat.
The work around I made on my W2K box (Tomcat 3.3a with J2EE 1.3.1):
I created a temporary directory: d:\mine_j2ee_classes and unzip j2ee.jar to this directory. Then I renamed d:\mine_j2ee_classes\org\apache to d:\mine_j2ee_classes\org\apache_orig. After that, I added d:\mine_j2ee_classes to my Tomcat classpath, and it works fine. By doing this, I use J2EE as the JMS provider, but only use Tomcat's apache.* implementation.
Ye

JMS Adapter question

Hi,
Is it possible to use a different jndi-factory other than teh default WL one: weblogic.jndi.WLInitialContextFactory?
also if my jms accepts only client cert ssl authentication, is it possible to setup this in Oracle CEP? I am getting all kinds of errors
when I try to do any of the above and the documentation seems to layout only default scenarios so not enough details. I am getting this error:
org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.Exception: Error initializing JMS connection: javax.naming.NoInitialContextException: The JNDI initial context factory "com.sun.jndi.fscontext.RefFSContextFactory" either cannot be loaded or it does not exist.
I added all required jar files for this jndi-factory in runtime lib in Manifest.mf but it is not loading at all.
Anybody tried something similar to this? any pointers?
Thanks,
Firas

Hi Andy,
I changed it to Debug and got the following stack:
<Mar 10, 2010 2:53:46 PM EST> <Notice> <Deployment> <BEA-2045000> <The application bundle "mmxHelloWorldd" was deployed successfully to file:/E:/oracle/Middleware/user_projects/domains/ocep_domain/defaultserver/applications/mmxHelloWorldd/mmxHelloWorldd.jar with version 1268250825479>
<Mar 10, 2010 2:53:50 PM EST> <Debug> <Adapters> <BEA-000000> <InboundJmsAdapter.beforeResume was called>
<Mar 10, 2010 2:53:50 PM EST> <Debug> <Adapters> <BEA-000000> <JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
java.lang.ClassCastException: javax.naming.Reference
     at com.bea.wlevs.adapters.jms.JmsAdapter.beforeResume(JmsAdapter.java:109)
     at com.bea.wlevs.adapters.jms.InboundJmsAdapter.beforeResume(InboundJmsAdapter.java:74)
     at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$FastClassByCGLIB$$fc18e7ee.invoke(<generated>)
     at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
     at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
     at com.bea.wlevs.eventstore.recplay.RecordPlayProxy.invoke(RecordPlayProxy.java:255)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
     at com.bea.wlevs.monitor.internal.MonitoringProxy.invoke(MonitoringProxy.java:165)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)
     at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$EnhancerByCGLIB$$b6867280.beforeResume(<generated>)
     at com.bea.wlevs.spring.ActivationBeanPostProcessor.preProcessBeforeContextResume(ActivationBeanPostProcessor.java:27)
     at com.bea.wlevs.spring.DeferredBeanPostProcessor.beforeResume(DeferredBeanPostProcessor.java:33)
     at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:114)
     at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
     at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
     at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
     at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
     at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
     at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
     at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
     at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
     at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
     at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
     at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
     at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
     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)
>
<Mar 10, 2010 2:53:50 PM EST> <Error> <Deployment> <BEA-2045010> <The application context "mmxHelloWorldd" could not be started: org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.Exception: JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.Exception: JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
     at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:136)
     at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
     at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
     at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
     at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
     at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
     at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
     at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
     at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
     at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
     at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
     at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
     at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
     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)
Caused By: java.lang.Exception: JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
     at com.bea.wlevs.adapters.jms.JmsAdapter.beforeResume(JmsAdapter.java:120)
     at com.bea.wlevs.adapters.jms.InboundJmsAdapter.beforeResume(InboundJmsAdapter.java:74)
     at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$FastClassByCGLIB$$fc18e7ee.invoke(<generated>)
     at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
     at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
     at com.bea.wlevs.eventstore.recplay.RecordPlayProxy.invoke(RecordPlayProxy.java:255)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
     at com.bea.wlevs.monitor.internal.MonitoringProxy.invoke(MonitoringProxy.java:165)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)
     at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$EnhancerByCGLIB$$b6867280.beforeResume(<generated>)
     at com.bea.wlevs.spring.ActivationBeanPostProcessor.preProcessBeforeContextResume(ActivationBeanPostProcessor.java:27)
     at com.bea.wlevs.spring.DeferredBeanPostProcessor.beforeResume(DeferredBeanPostProcessor.java:33)
     at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:114)
     at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
     at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
     at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
     at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
     at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
     at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
     at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
     at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
     at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
     at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
     at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
     at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
     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)
>
<Mar 10, 2010 2:53:50 PM EST> <Notice> <Deployment> <BEA-2045001> <The application bundle "mmxHelloWorldd" was undeployed successfully>

J2EE question.. ftp in a session bean

Hi guys,
pretty new to j2ee. I need to make a system that retrieves some files using ftp and manipulate teh files and return to a servlet the link to file (which will live on a webserver).
I read that java.io package should not be used with ejb's. the MDB thats using the ftp api that i created seems to run fine, with no errors. However the files aren't showing up. Am i missing something here?
I give an absolute path to where the files should be downloaded. all i know is that the files don't show up there and that tehre are no exceptions. Could weblogic be storing the files somewhere else?
can ejb's give make directories adn files on the server where they're running?
where does "/" refer to when given in a ejb? is it the root of the file
system or some other location?

grr.. never mind.. its working
sorry!

JMS Adpater Question

I am trying to implement the JMSAdapter in the two way mode.
I have configured the queues and have configured the JMS Adapter appropriately.
I do see the response being generated but the correlation doesn't seem to work.
Error Message:
Fault ID rejected:60006
Fault Time Apr 13, 2012 4:44:31 AM
Non Recoverable System Fault :
Cannot complete callback since unable to retrieve SourceURI/Wire from Correlation store. Either Instance Tracking is diabled or no corresponding Request succeeded prior to this callback
The payload details for this rejected message can be retrieved
Any idea what's missing??
I do see the response message on the queue.

Got it to work....had missed setting the Correlation ID in my JMS application :) my bad ..:)

JMS Specification Question regarding persistent messages and reliability.

In section 6.15 of the JMS Specification, titled reliability it is stated that:
"When all messages for a topic must be received, a durable subscriber should be used. JMS insures that messages published while a durable subscriber is inactive are retained by JMS and delivered when the subscriber subsequently becomes active.
Nondurable subscribers should be used only when missed messages are tolerable."
Then in a table following the above text it states that a nondurable subscriber on a topic flowing persistent messages will receive a message "once-and-only-once (missed if inactive)."
To me this implies that if a nondurable subscriber is active, it is guaranteed to receive all persistent messages published to the topic while it is active. However there seems to be some ambiguity about what it means to be "active." Does active mean subscribed, does it mean subscribed and not busy processing messages, something else?
I ask this because I'm seeing a somewhat slow subscriber not receiving all persistent messages published while it is subscribed. This was surprising to me, given my interpretation of this reliability clause, so I'm wondering if I have not interpreted it correctly in this case.
Could anyone fill me in, particularly if you had something to do with writing the spec or can point me to the rationale behind this portion of the spec?
Thanks,
Jeff Singer

I am looking at the JMS 1.1 Spec version 1.1 April 12, 2002.
Section 4.10 "Reliabilty" has what reads to me as kind of a CYA statement that the contributing JMS providers got inserted. It reads:
"A JMS provider may have resource restrictions that limit the number of messages that can be held for high-volume destinations or non-responsive clients. If messages are dropped due to resource limits, this is usually a serious administrative issue that needs attention. Correct functioning of JMS requires that clients are responsive and that adequate resources to service them are available.
+
+
+Once-and-only-once message delivery, as described in this specification, has the important caveat that it does not cover message destruction due to message expiration or other administrative destruction criteria. It also does not cover loss due to resource restrictions. Configuration of adequate resources and processing power for JMS applications is the job of administrators, who must be aware of their JMS provider's reliability features."
+

JMS J2EE question

Similar Messages

Maybe you are looking for