How to tell if an instance of a bean has been created?

Question

I'm trying to deploy a message driven bean, and from what I can tell it seems to deploy fine. I say this because it deploys my ear successfully and has INFO messages which seem to say all ejb(s) loaded successfully!.
However, I have tried to setup a pool of my mdb, so that a couple of instances pre-load. Here is my sun-ejb-jar.xml file:
<sun-ejb-jar>
<enterprise-beans>
<unique-id>1</unique-id>
<ejb>
<ejb-name>LoggerEJB</ejb-name>
<jndi-name>com.ecc.utils.LoggerTopic</jndi-name>
<mdb-connection-factory>
<jndi-name>com.ecc.utils.JMSTopicConnectionFactory</jndi-name>
</mdb-connection-factory>
<bean-pool>
<steady-pool-size>2</steady-pool-size>
<resize-quantity>1</resize-quantity>
<max-pool-size>5</max-pool-size>
<pool-idle-timeout-in-seconds>600</pool-idle-timeout-in-seconds>
</bean-pool>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
As you can see, I'm trying to get 2 of them to be loaded in memory at all times. However, I don't believe it's acutally doing it. The reason is, I have System.out.println statments to output information on ejbCreate and other load steps that I'm not seeing in the main app server window. Shouldn't I see the output from the System.out.println statements?
Also, the mdb is looking for a data source that shouldn't exist, so I should see output from the .printStackTrace statement I have from catch the exceptions, and I'm not seeing those as well.
Finally, I even setup the mdb to write to a text file when it does load, and I can't find the file anywhere under the /AppServer7 directory. All this leads me to believe it is NOT loading any instances of my mdb.
Sooo, is there a way to tell if and how many instances of a bean are loaded? Also, if my depoyment descriptor is wrong, how do I fix it to pre-load instances of my mdb?
And, if it IS loading, where is my system.out.println and .printstacktrace output?
Thanks, Tony

Answer 1

Look in the app store - there are many apps that do anti theft tracking. Many can be defeated by factory resetting the device - it is simply the nature of how Apple restrict developers from locking an app to a device. A factory reset can be done in iTunes 'restore device' or via Settings > Reset, 'erase content & settings' in iOS.
If the company used iCloud for anti theft tracking you can't avoid it being reassociated with iCloud after a factory reset.
I also believe OS X server has similar features for anti theft tracking for corporate customers. So the device may be tied to an OS X server within the company, it;s unclear if the device will become reassociated, it depends on the company setup IIRC.
The simplest answer is to get the company IT to remove whatever they used. If you want to be certain there is no other jailbreaks on the device just factory reset it. That will also remove any data left over from a previous owner.