EJB 3.1 Lite Features Async,Timers ?

Hi
I was using glassfish 3.0.1 ,EJB 3.1 timers and async methods were working (in gfish 3.0.1). Now we are moving to glassfish 3.1, And I'm getting following error with EJB 3.1 lite web application.
java.lang.RuntimeException: Invalid application. EJB WorkerBean defines asynchronous session bean methods. This feature is not part of the EJB 3.1 Lite API
Please suggest me any workarounds.
-raghu

user3923437 wrote:
Thanks for your response. Now I understand the problem. Actually I'm using glassfish 3.1 nightly builds(as it's not yet released). So web profile is active in the glassfish runtime. Ok I need to wait for main release.
-raghuEither you were mistaken, or Glassfish V3.1 was very recently released.
http://glassfish.java.net/downloads/3.1-final.html
Make sure to get the right download, or you'll end up with the web profile again.

Similar Messages

Question to understand VRF and VRF-lite features

Hi,
when I look at METRO switches Feature list I see that most of them support only "VRF-Lite".
Does it mean that they can't work with MPLS lables and can't be placed as PE devices in cases where we need VPN services or any kinf of "Lable-switching" services?
Which role then does those METRO switches play in a network?

Hello Konstantin,
VRF lite is a subset of MPLS L3 VPN features missing MPLS forwarding plane capabilities.
An end to end dedicated IP path is needed for each VRF, practically a VRF-lite capable device should be connected to a fully capable PE node by using a L2 trunk and dedicating at least two Vlan and two SVI for each VRF: one towards customer and one towards PE.
you get a multi VRF CE that can be shared by multiple customers
a fully capable PE node uses N+1 links for N VRFs, a multiVRF CE requires 2*N logical interfaces for N VRFs
only one MPLS enabled backbone link is needed for handling traffic of multiple VRFs in a fully capable PE node.
in metro ethernet VRF lite multi VRF CE are used as feeders sort of satellite of PE nodes to provide an access layer to customers
Hope to help
Giuseppe

EJB 3.1 @Asynchronous and calling other methods from within

Hey all,
I am helping a friend set up a test framework, and I've turned him on to using JEE6 for the task. I am decently familiar with entity beans, session beans, and such. One of the new features is @Asynchronous, allowing a method to be ran on a separate thread. The test framework generally needs to spawn potentially 1000's of threads to simulate multiple users at once. Originally I was doing this using the Executor classes, but I've since learned that for some reason, spawning your own threads within a JEE container is "not allowed" or bad to do. I honestly don't quite know why this is.. from what I've read the main concern is that the container maintains threads and your own threads could mess up the container somehow. I can only guess that this might be possible if your threads use the container services in some way.. but if anyone could enlighten me on the details as to why this is bad, that would be great.
None the less, EJB 3.1 adds the async capability and I am now looking to use this. From my servlet I use @EJB to access the session bean, and call an async method. My servlet returns right away as it should. From the async method I do some work and using an entity bean store results, so I don't need to return a Future object. In fact, my ejb then makes an HttpClient call to another servlet to notify it that the result is ready.
My main question though, is if it's ok to call other methods from the async method that are not declared @Asynchronous. I presume it is ok, as the @Asynchronous just enables the container to spawn a thread to execute that method in. But I can't dig up any limitations on the code within an async method.. whether or not it has restrictions on the container services, is there anything wrong with using HttpClient to make a request from the method.. and making calls to helper methods within the bean that are not async.
Thanks.

851827 wrote:
Hey all,.. from what I've read the main concern is that the container maintains threads and your own threads could mess up the container somehow. I can only guess that this might be possible if your threads use the container services in some way.. but if anyone could enlighten me on the details as to why this is bad, that would be great.
Yes since the EE spec delegated thread management to conatiners, the container might assume that some info is available in the thread context that you may not have made available to your threads.
Also threading is a technical implementation detail and the drive with the EE spec is that you should concentrate on business requirements and let the container do the plumbing part.
If you were managing your own threads spawned from EJBs, you'd have to be managing your EJBs' lifecycle as well. This would just add to more plumbing code by the developer and typically requires writting platform specific routines which the containers already do anyway.
>
None the less, EJB 3.1 adds the async capability and I am now looking to use this. From my servlet I use @EJB to access the session bean, and call an async method. My servlet returns right away as it should. From the async method I do some work and using an entity bean store results, so I don't need to return a Future object. In fact, my ejb then makes an HttpClient call to another servlet to notify it that the result is ready.
My main question though, is if it's ok to call other methods from the async method that are not declared @Asynchronous. I presume it is ok, as the @Asynchronous just enables the container to spawn a thread to execute that method in. But I can't dig up any limitations on the code within an async method.. whether or not it has restrictions on the container services, is there anything wrong with using HttpClient to make a request from the method.. and making calls to helper methods within the bean that are not async.
Thanks.If you want to be asynchronous without caring about a return value then just use MDBs.
The async methods have no restrictions on container services and there is nothing wrong with calling other non async methods. Once the async method is reached those annotations don't matter anyway (unless if you call thhose methods from a new reference of the EJB that you look up) as they only make sense in a client context.
Why do you need to make the call to the servlet from the EJB? Makes it difficult to know who is the client here. Better use the Future objects and let the initial caller delegate to the other client components as needed.

EJB 3.0 Security with ACEGI and not with Container Managed Security

Hi,
     Currently we are using EJB 2.0 in our project, We want to use EJB 3.0
     But for security we want to use Spring ACEGI Security and we don�t want to use container managed security (No Portability, Difficult, �)
     ACEGI supports Servlet/JSP security very well (I am able to call isUserInRole(), getUserPrincipal() because ACEGI implements by ServletRequestWrapper in a filter)
     But for EJB, it lacks this feature. (There is no standard EJB interceptor API as there is with servlets (using filters), so there's no generic way of modify in the EJB context for the invocation)
     Without using container managed security, Is there any way to propogate my security context from Servlet Layer to EJB Layer, So that I can use EJB Declartive security and getCallerPrincipal(), isCallerInRole() API.
     For more info please see this thread http://forum.springframework.org/showthread.php?t=26514
     Why don�t you provide standard EJB interceptor API as there is with servlets (using filters), so there I am able add security identity to EJB context.
     I am eagerly waiting for the reply

Reason: javax.naming.NameNotFoundException: jdbc not bound
Although i am quite new to this as well i would say that there is a problem with your connection with the database.
It seems it cannot connect to Mysql.
have you download the mysql package library and imported it ?
Also in your deploy folder in you Jboss
have you altered the jdbc to connect to you database in your dataset ? ( i am not sure about mysql, but postgre reguired this)
Most probably it would be the same in mysql.
<connection-url>jdbc:postgresql://127.0.0.1:5432/Dissertation</connection-url>
Not sure if this is what you reguire, i am new at this my self

Using Dynamic Proxy in AppServer 7 during EJB deploy

Hello Guys.
I know Dynamic Proxy is the default when deploying EJBs starting from AS 8.1. If I want to use Dynamic Proxy in AS before 8.1, how can I do that?
Thanks.
Rye

Just to clarify, I assume you're referring to the Remote EJB dynamic RMI-IIOP feature in 8.x and later.
Java SE has a generic dynamic proxy facility in the java.lang.reflect package. That can of course
be used by any JDK 1.4 program and has no relationship to Java EE.
There is no support for the Remote EJB dynamic RMI-IIOP feature prior to AS 8.x / J2EE SDK 1.4.
In those releases, e.g. S1AS 7.x / J2EE 1.3 SDK , static RMI-IIOP stubs are generated during
deployment and must be present for any client access to Remote EJBs.
--ken

Async timer stall behavior

In service to my unending quest to understand async timers ...
I have an app with two async timers, each with its own callback, and I understand both run on the same thread.
So if one of the callbacks stalls, will the other ever get scheduled? If they're truly on the same, single thread, then if you lock up one of the two callbacks (e.g. put it into an endless loop), then the other callback should never get called.
Thanks.
Solved!
Go to Solution.

Thanks for the info!
Yes, I had seen behavior over long runs (application runs for weeks at a time, constantly using two async callbacks) that caused me to believe there was some unobvious semantic to the async timer scheduling, which you've just explained. If this is NI implmentation detail, it's never been explained anywhere that I can find.
I do need to prevent the 30 second callback from taking longer than the timer period - it normally doesn't, and in that case everything works as expected.
I create the 15 second timer first, and that's the one that continues to get callbacks after the 30 sec timer stops getting its.
What I still don't have a grip on, is that if it's the 15 second timer that gets priority, and it has enqueued a bunch of callbacks missed because the 30 second timer was stuck in it's callback, why doesn't the 15 second timer flush out all of it's enqueued callbacks once it's able to? Otherwise, queueing them up doesn't make sense. I would have thought that the 15 sec timer would flush it's enqueud callbacks out as fast as they were serviced, and then both timers would resume getting their callbacks per their schedules.
Here's my code:
#define POLL_INTERVAL 15
#define CONTROL_INTERVAL 30
// Create polling and control async timers, start callbacks
iPollTimer = NewAsyncTimer (POLL_INTERVAL, -1, 1, MeasurementPoll, 0);
iControlTimer = NewAsyncTimer (CONTROL_INTERVAL, -1, 1, Control, 0);
Another thought I have is that this is a fast, 8 core PC. I wonder if there's some weirdness getting in due to the true parallel execution that can take place, though the async timers are on the same thread so shouldn't be a race there.
When the 30 sec timer stops getting callbacks, the 15 sec timer callback interval gets stretched out to about 25 seconds - up until then, I see the expected, regular 15 and 30 sec callbacks.
Thanks again.

Need help on VRF lite

I have implement VRF lite feature for one of the customer...it's working fine..But i m not so clear of following command ...........Can any one explane the same.
router ospf 511 vrf abc
capability vrf-lite <--------What is use of this command..is this is reletaed to BGP to OSPF redistribution..?

Hi,
VRF lite converts the router into multiple virtual routers each one with its separated routing table, interfaces and routing protocols.
The OSPF Support for Multi-VRF on CE Routers feature provides the capability of suppressing provider edge (PE) checks that are needed to prevent loops when the PE is performing a mutual redistribution of packets between the OSPF and BGP protocols. When VPN routing and forward (VRF) is used on a router that is not a PE (that is, one that is not running BGP), the checks can be turned off to allow for correct population of the VRF routing table with routes to IP prefixes.
When the OSPF process is associated with the VRF, several checks are performed when link-state advertisements (LSAs) are received. PE checks are needed to prevent loops when the PE is performing a mutual redistribution between OSPF and BGP interfaces. In some situations, performing PE checks might not be desirable. The concept of VRFs can be used on a router that is not a PE router (that is, a router that is not running BGP). With the capability vrf-lite command, the checks can be turned off to allow correct population of the VRF routing table with routes to IP prefixes.
This command suppresses the Provider Edge (PE) specific checks on a router when the OSPF process is associated with the VRF.
HTH, please do rate all helpful posts,
Mohammed Mahmoud.

Gui timer v/s Async timer priority

Hi NI,
I am trying to build an application where in i am communicating with an automotive ECU over RS-232 periodically. I am using an aysnc timer to do the communications part and a GUI timer to do the graphical object update. I have three questions for your team.
1. What RTOS and PC configuration do you recommend for using a RT Async Timer with Prority ? (preferably whats available in the market today in terms of "cheap" hardware)
2. What is the priority of the GUI timer when compared to the Async timer? Is is possible for the GUI timer to inetrrupt the Async timer fucntion call ? If yes...is there an exclusion mechanism that would stop this from happening ?
3. I am using a two linked list concept...the first list populates while the other's data is being drawn on the strip chart...and then i flip over to populating the second linked list while the first lists data is being plotted. The communications(population of data in a structure in a linked list) is being done in the Async thread while the plotting is being done in the GUI thread. The issue i am facing is that i do not have a clean linked list population, plotting and freeing of data sequence...i feel this is due to some un-predictability in the timer function calls.(hence Q2 above). Do you recommend only using thread safe queues or do you think this is do-able with linked lists.
Looking forward to your reponse.
-Ashish

I don't know what degree of certainity you need but a "fixed calling and execution sequence" is just a dream in a Windows environment.
Windows will operate your threads together with many more of its own, all with varying priorities.
So, you should think of priority as a vague way of making one thread to be operated more/less than another lower/higher degree thread.
No thread priority class guarantees a certain frequency of thread execution.
GUI timer callbacks are executed in the main program thread while async timers are executed in a seperate thread.
So, yes their execution times may coincide. Hence the need to protect your global data.
Data accessed by multiple threads should be protected so that, no thread would be interrupted in the middle of a write/read operation on that data.
TSQs do that for you. Otherwise you cannot be sure about the integrity of the data you are plotting.
If you need do some more reading about this. But TSQs stand out as a more elegant way to solve your problem.
S. Eren BALCI
www.aselsan.com.tr

Async timer slows operation down

Having previously used asynchronous timers to resolve another problem that I had, I'm now looking at an issue that has got me stumped
Here is a code snippet which has had an asynchronous timer applied
int CVICALLBACK ParentEvent (int reserved, int control, int event, void *callbackData, int eventData1, int eventData2)
static int iInfoFlag = 1;
//If Com Timer event has occurred then:
if (event == EVENT_TIMER_TICK)
SetAsyncTimerAttribute(control,ASYNC_ATTR_ENABLED, 0);
//First, has sonde configuration changed?
if (iSondeConfigure_HasChanged() == YES)
//Re-initialise displays etc, if true
InitialiseSondeSystems(iFloatingPanels);
//Get Sonde data
if (ProgStatus.bComTimerEvent == TRUE)
CompactDataControl (hParentPanel, iInfoFlag, &ProgStatus, NULL);
//If Com events are disabled then set Sonde Info flag for next data
//acquisition sequence
if (ProgStatus.iComEnable != ENABLED)
iInfoFlag = 1;
SetAsyncTimerAttribute(ParentTimer,ASYNC_ATTR_ENABLED, 1);
return(0);
This routine was previously handled by a conventional timer but as these sit at the bottom of the pile when it comes to scheduling, as soon as the interface was manipluated it shut up. The timer in each case is set at 0.1 second, and if the bComTimerEvent flag is set to true, which is controlled by another (currently traditional timer) it goes away and grabs data from an external source. Using traditional timers, I can clock this 'grab the data' timer quite happily at 0.25 seconds. However with the code shown, it wont grab data any faster than about 1.5 seconds. I have timed how long it takes to call and return from CompactDataControl. With traditional timers its about 0.2 seconds, with the code as shown, its about 1.45 seconds.
Any thoughts as to what I've missed or messed up.
Regards
Gavin
Solved!
Go to Solution.

All I'm doing is calling Timer() before and after a particular function, and working out how long it takes... I've done this with both normal, and async callbacks and got significant differences. I think due to the nature of what has been done already, this code will need the same treatment as the last project I worked on that required async timers, which was a complete rewrite from the ground up. What is interesting is that that project does make changes to the GUI based on the async timers, without any obvious performance issues, despite of the fact that elements of the GUI are created in the main thread. However this project is doing an awful lot more, which might in someway explain this.
I'd be interested to know if there is any way you can use traditional timers without the problems of timers stopping, when moving or resizing the GUI - the thing I am try to prevent by using async timers
However I think what youre saying about your use of Async timers for number crunching, and standard timers for GUI update is a good idea, and I'm pretty sure would work for me.

Flyer - Open Source Python Framework for Flash Lite Developers

I’m pround to announce the first release of Flyer.
Flyer was built to extend Flash Lite features with Python for S60.
Flyer is based on the Flash Lite 2.1 integration with Python
for S60 and contains the following features:
- Take photos with device camera from Flash Lite
- Take device screenshots from Flash Lite
- Send files over a bluetooth connection from Flash Lite
- Get the contact entries in the default device database
Future releases (May, 2007)
- Sound recording and playback
- File upload to a remote server
- GPS module to display latitude, longitude, satellite count,
and time
- Record device screen
Project Home
Get Flyer Running on your
mobile device

Sorry Romu, but this against the CoC and [Terms of use|http://www.sun.com/termsofuse.jsp#g2_1] here.

M-Series read + Write, threading or async , performance issues

I have a slightly unusual issue: Using 2 USB-6251 and 2 USB-6015 within the same application.
1 of the USB-6251s reads data on a 50 msec look (Driven by an async timer).
Depending on the input the code decides to output a 40 Hz, 300 usec waveform of varying amplitude - the output goes one until there is a user event that might make it stop.
Now , here is the problem. I have implemented the output function using a sepereate high priority thread and the delay( delay_in_sec) command.
I find that while the data acquisition timer is NOT running the frequency of the output is very close to 40 Hz. When the data acquisition IS running , the frequency of the output varies considerably - most likely reflecting USB delays.
I was able to see the output 40Hz, 300 usec waveform using a seperate app using a single async timer w/o any data acq and the timing was immaculate.
My questions are:
1. Could I use 2 different async timers in the same app - I tried to do this and the output was still wacky when I turned data acquisition on
2. Is there any way outside the delay() command that could improve the timing accuracy of the analog output thread?
3. I measured the time to create a 300 usec pulse of a certain amplitude, write it to the USB-6251 and start the task and it was ~ 13 msec. This is way too slow for 300 samples at 1 MHz - is it a USB bus limitation, or I should look at my design to see what is going on?
4. Any NI hardware that would allow me to handle 4 analog outputs more gracefuly? (FYI, 2 of my outputs are at 1 MHz and 2 of them at 50 Hz).
Thanks
AP

THanks for taking the time to look at my message.
I am using 4 DAQs. First one, USB-6251 is used to collect data (4 analog inputs @ 20Hz) and also occasionally provide analog output @ 1 MHz.
Second DAQ is a USB-6251 occasionally provide analog output @ 1 MHz.
Third and Fourth DAQ areUSB-6015 occasionally providing analog output @ 50 Hz.
All devices are connected via USB to a Dell Dual Core notebook.
THis is how I create & configure the analog output channels - using 1 task per device.
                    DAQmxErrChk(DAQmxCreateAOVoltageChan(TaskAnalogX,channelstring , "Ramp 1",0 , 10, DAQmx_Val_Volts, ""));
                   DAQmxErrChk(DAQmxCfgSampClkTiming(TaskAnalogX, "",1MHz OR 50Hz, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps     , SECONDS*1MHz));
                   DAQmxErrChk(DAQmxWriteAnalogF64 (TaskAnalog1, ( int32 )SECONDS*1MHz OR 50Hz ), 0, DAQmx_Val_WaitInfinitely, DAQmx_Val_GroupByChannel , PHAOarr, &sampsPerChanWritten, NULL));
THe design/architecture is pretty complex but on a very high level whenever I need to deliver analog output I configure the output waveforms and then write it to the DAQs and then use some timers/logic to deliver the waveform from the DAQ as needed.
Now the challenge has been that in one specific case I need to deliver analog output of uknown duration (whereas everything else is deterministic). In that case i created a seperate thread and write each 300 usec pulse individually to the analog output (using USB 6251)using the following tASK:
                    DAQmxErrChk(DAQmxCreateTask("Tonic Output Task", &TaskTonic));
                   DAQmxErrChk(DAQmxCreateAOVoltageChan(TaskTonic, channelstring , "PulseToPulse",0 , 10, DAQmx_Val_Volts, ""));
                   DAQmxErrChk(DAQmxCfgSampClkTiming(TaskTonic, "",1.0E+06, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps , 301));
As described in my first message this is very sensitive to timing and it takes 13 msec to stop the task , write the array to the DAQcard and then start the task again.
On the hardware timing recommendation. I tried to configure the DAQ using the DAQmx_Val_HWTimedSinglePoint samplemode but it seems not to be supported by the hardware I am using. Is there a CVI example of using hardware timing that I can take a look at?
THanks
AP
Hi AP,
My first impression is that you would want to use hardware timing
rather than software timing. Try using a DAQmx Timing command and
specify the rate there. Aside from that, could you be more specific
about your application? How do you have your hardware set up and which
devices are handling each part of the task? How are you generating the
output?
Regards,
Joe S.

Timers In Multitreading

Hi,
Am working ona application which receives data from four COM ports simentaniously,i have implemnted four threads to receive each of the channel.
i have a timing requirement for each channel, means i should read each channel at a diffrent interval 10,15,10,25 msec respectively.
what would be the best way to implement the timer for each of the tread independently to make it continuiosly receive in the above mentioned time frame until user stops the application.
Thanks in Advance

As far as I can understand, all callbacks will be executed in the same thread. This implies that under some circumstances some timer callback can never be executed: callback lenght is crucial here (see D_Biel post and code here in the thread I posted earlier: experiment with the code as is and by running timer2 before timer1).
I can think of a more complex architecture that may be able to sustain your requirements: it won't be trivial to trim it at best but on modern multicore PCs I suppose is the best you can have:
At program start launch four different threads, one for each COM port to handle; threads mus be sitting in a loop that processes events, possibly with some small delay in it. Save thread IDs for use in the timer callbacks
Launc your 4 async timers with required intervals
Timer callbacks will simply PostDeferredCallToThread the required function, using the appropriate thread ID saved before. Make sure that launched callbacks do not last more that the corresponding timer interval
Provide a mean to stop all threads at program end
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

EJB Configuration Assistance Required

Hello,
I am new to EJB deployment, and I'm currently having some issues configuring Weblogic8.1 to recognise a sample "timer" ejb I found an example of.
The following line always fails on first startup of the application server;
EmailTimerHome timerDemoHome = (EmailTimerHome)PortableRemoteObject.narrow(context.lookup("java:comp/env/ejb/EmailTimer"), EmailTimerHome.class);
with the line
javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/EmailTimer in /app/webapp/bpwise/3231848.; remaining name 'comp/env/ejb/EmailTimer at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic NamingNode.java:858)
My configuration files are as follows;
ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<description>Session Bean ( Stateless )</description>
<display-name>EmailTimer</display-name>
<ejb-name>EmailTimer</ejb-name>
<home>com.logicacmg.bpwise.web.timers.EmailTimerHome</home>
<remote>com.logicacmg.bpwise.web.timers.EmailTimer</remote>
<ejb-class>com.logicacmg.bpwise.web.timers.EmailTimerBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-ref>
<ejb-ref-name>ejb/EmailTimer</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.logicacmg.bpwise.web.timers.EmailTimerHome</home>
<remote>com.logicacmg.bpwise.web.timers.EmailTimer</remote>
</ejb-ref>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>EmailTimer</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
and weblogic-ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE Weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD Weblogic 8.1.0 EJB//EN'
'http://www.bea.com/servers/wls810/dtd/Weblogic-ejb-jar.dtd'>
<Weblogic-enterprise-bean>
<ejb-name>EmailTimer</ejb-name>
<reference-descriptor>
<ejb-reference-descriptor>
<ejb-ref-name>ejb/EmailTimer</ejb-ref-name>
<jndi-name>com/logicacmg/bpwise/web/timers/EmailTimerHome</jndi-name>
</ejb-reference-descriptor>
</reference-descriptor>
</Weblogic-enterprise-bean>
I've obviously went completely off-track somewhere. Any help would be appreciated.
Thanks,
Mark.

nosredna wrote:
> I am running the Developer version of CFMX 7 and using
the internal web server.
> It uses the default port 8500. Everything works fine for
my development of
> this site. I now want to implement a second "website" to
do development work
> and am wondering how to accomplish this. Do I need to
uninstall CFMX7 and
> re-install it using the multiserver configuration? Can I
just set up a new
> port (e.g. 8501) with a separate directory (e.g.
wwwroot2)? Any guidance would
> be appreciated.
>
> Thanks.
>
You do not need to re-install CF in multi-server. The single
ColdFusion
instance you are running can handle as many web sites as you
care to
load it down with. Multi-server is for having multiple
ColdFusion
instances running. Each configured to handle one or more web
sites for
application isolation and|or clustering and|or fail over
purposes.
What I do not know is if the built in internal web server can
be
configure to serve up multiple web sites. I have never used
it. I
always install Apache or IIS or PWS (Personal Web Server,
back in the
day) and configure as many web sites I want all connected to
my Cold
Fusion server.
You may want to go with one of these other web server
applications and
switch from the internal one. I believe there is a way to do
this, but
again, since I have never used the internal web server I am
not familiar
with switching procedures.

Super 1.5 - source code level tracing for EJB, JSP and others

Would you want to try new installation for Super 1.6?
Please visit www.acelet.com
Thanks.
"Dominique Jean-Prost" <[email protected]> wrote:
If only your installation tool was easy to use ...
dom
"Wei Jiang" <[email protected]> a écrit dans le message news:
[email protected]...
Super supports source code level tracing for Java and JSP!
Announcement: Super 1.5 - an EJB/J2EE monitoring tool with
SuperPeekPoke
SuperLogging
SuperStress
SuperEnvironment
It is free for development.
You can anomyously down load it from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A PeekPoke tool to read/write attributes from EJBs.
* A full-featured logging/tracing tool for centralized, chronologicallogging.
* A Stress test tool.
* A global environment tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1
* Weblogic 6.0
What is new:
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView,TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView andPieView.
Changes:
1. The structure of log database changed. You need delete old installationand
install everything new.
2. The format of time stamp of SuperLogging changed. It is not localedependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clusteringenvironment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not bestopped
and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, itis
treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabasecan
be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be emptyfor
Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods willnot
try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put logdatabase
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDIname
(mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it worksfor
both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2and
1.3
Changes:
1. All changes are backward compatible, but you may need to recompilemonitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message willnot
show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: pressF1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.

Thread vs async timer in labwindows

i have a program in which i have to aquire / send data from serial port which is time critical ie 10 ms , my quension is that what are my options, can i use threads or use asynctimer (that can have 16 independent threads). i understand how to use asyncronus timer but my question is that are there anyother ways of creating threads in labwindows and are they as effective as asyncronous timer, please guide me in detail.
thanks in advance
regards ahsan

Well, async timers are an implementation of multithreading that rely on Windows multimedia timers for scheduling events; you may consider it as an application of multithreading. It's intended to give users an easy instrument to begin programming in multithreading without much effort: you can develop and debug your app using a UI timer and then switch it to async timer to execute it in a multithreaded environment without even changing the callback definition!
At the same time, this paradigm includes some constraints that may be not optimal in search for an optimized application.
Having said this, you must consider that maintaining a 10 ms regular pace with no-missing-codes requirement over a long time is *really* a difficult task, if not impossible on Windows: there are so many underlying tasks in this OS that you are never guaranteed that none of them will interrupt you at some moment. Trying to achieve this goal will imply a lot of work aimed to:
- make your app highly efficient
- tailor the OS to close or reduce time consuming activities that may interfere with your app (antivirus; automatic updates; scheduled tasks; unnecessary services; including some from NI...)
Frankly speaking, the 10ms constraint would claim for a real time environment, not for a Windows program!
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

EJB 3.1 Lite Features Async,Timers ?

Similar Messages

Maybe you are looking for