EJB 3.0 Locking (entity not in the persistence context)

hi all,
i have some problems about locking,
i have 1 remote and one local interface
1. Remote Interface
public @Stateful
@Remote(RemoteInterface.class)
class RemoteInterfaceBean implements RemoteInterface
       @PersistenceContext(unitName = "CustomerCareOracle")
     private EntityManager oracleManager;
        public MySomeEntityObject object;
       @EJB
        MyLocalInterface inter;
    @TransactionAttribute(TransactionAttributeType.REQUIRED)
    public void fillMyObject(someparameters .... )
      // filling MySomeEntityObject object
    @TransactionAttribute(TransactionAttributeType.REQUIRED)
    public void commitMyObject()
      inter.AnotherOperatOnObject(object);
      oracleManager.persist(object);
2. My Local Interface
public @Stateless
@Local(MyLocalInterface.class)
class MyLocalInterfaceBean implements MyLocalInterface
       @PersistenceContext(unitName = "CustomerCareOracle")
     private EntityManager oracleManager;
        @TransactionAttribute(TransactionAttributeType.REQUIRED)
         public void AnotherOperatOnObject(MySomeEntityObject object)
               oracleManager.lock(object,LockModeType.READ);
// <= Here I Got An Error
               // do some operation and is succsess, It's very good ;)
}     when i tryed to lock object i got an error, i can't resolve this problem :(
can anybody help me ?
error trace
17:43:21,343 ERROR [errorCat] java.lang.IllegalArgumentException: entity not in the persistence cont
ext
        at org.hibernate.ejb.AbstractEntityManagerImpl.lock(AbstractEntityManagerImpl.java:336)
        at org.jboss.ejb3.entity.TransactionScopedEntityManager.lock(TransactionScopedEntityManager.
java:101)
        at com.magti.businesslayer.ejb3Fasade.oracle.ccare.TransactionFasadeBean.lockAccounts(Transa
ctionFasadeBean.java:203)
        at com.magti.businesslayer.ejb3Fasade.oracle.ccare.TransactionFasadeBean.doAfterCheck(Transa
ctionFasadeBean.java:76)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
        at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
        at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor
.java:63)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPer
sistenceContextPropagationInterceptor.java:57)     Regards,
Paata.

It looks like you're trying to call lock before the entity has been created within the persistence
context. Persist the entity within the persistence context before calling lock.

Similar Messages

Is there a solution to open the network locked iphone 6 Ali Sprint I've purchased iphone 6 from ebay and upon arrival I have to drag the device is locked and not supporting the network in Saudi Arabia

Is there a solution to open the network locked iphone 6 Ali Sprint
I've purchased iphone 6 from ebay and upon arrival I have to drag the device is locked and not supporting the network in Saudi Arabia

There is no solution other than to contact Sprint and ask them if they will unlock it.

TS3274 my ipad does not flip the visual context as I turn it

my ipaddoes not flip the visual context as I turn it. how do i fix it?

Is there a lock symbol at the top of the screen next to the battery indicator ? If there is, then depending on what you've got Settings > General > Use Side Switch To set to (rotation lock or mute notifications), then you can lock/unlock the rotation by the switch on the right hand side of the iPad above the volume switch, or via the taskbar : double-click the home button; slide from the left; and it's the icon far left; press home again to exit the taskbar. The function that isn't on the side switch is set via the taskbar instead : http://support.apple.com/kb/HT4085
If there isn't a lock symbol then try a reset : press and hold both the sleep and home buttons for about 10 to 15 seconds (ignore the red slider), after which the Apple logo should appear - you won't lose any content, it's the iPad equivalent of a reboot.

Not showing the available contexts?

Hi,
When I am running a report in WebI, its running fine. Wehn I open the report in Edit mode, in the query's its shown the context name in the query properties. When I try to edi the query, and even though, I restore the same objects in the query panel, its asking for context. But its not showing the actual context. Its showing other contexts.
Could anyone faced this kind of problem?
Any help pelase.
Thank you,
Regards,
Gowtham Sen.

Hi Gawtham,
I would suggest you look at the universe and check that the objects are being defined correctly i.e by checking the class and source table.field and double check that the contexts have been defined correctly.
Regards
Jacques

ZCM 11.2 DLU does not pass the full context

ZCM 11.2 and 11.2.1
ZCM 11 installed on windows server 2008 R2
Windows 7 64 users client NC2 4 and NC2 4a
Authenticating to Suse 11 OES 11 server
When a new user (student) logs into a workstation the user is created, the user does login, but then an error shows up that "You are already logged on as .user.vps do you still want to login. You can click no. and then retype the username and it finds the name just fine via contextless. This essentially creates a double login issue. Not bad if it is a permanent DLU, but a real pain in the rear for volitile dynamic users.
So it appears as if the user was created and authenticated, but then is trying to authenticate again. I do notice that the user context is incorrect. For instance students are actually located in:
.HS.students.vps so it should be .johndoe.hs.students.vps and the error indicates .johndoe.vps
Is this and ldap issue? A client issue? I did not have this problem with 11.2 before my ZCM server crashed. I now have a fresh install of ZCM 11 but on a windows box instead of directly on my suse 11 with oes11.

Is the "Allow Dots in UserName" enabled or Disabled in the Novell Client
for Windows 7?
(Sorry, I likely do not have the exact name correct.)
I would recommend disabling it if possible.
On 9/25/2012 8:46 AM, dixond wrote:
>
> spond;2216623 Wrote:
>> Dholland,
>>
>> TID 7010724 - no promises, but the fix for this is expected in 11.2.1
>> MU2 which is due in about 2 weeks, we hope
>>
>> --
>>
>> Shaun Pond
>
> We applied 11.2.1 MU2 last night and we are still unable to use long
> context. Any suggestions?
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

Why not use EXTENDED persistence context?

When would you not ever use EXTENDED persistence context in a stateful session bean (which is the only EJB type it can be used in)?
To me it seems that the code is cleaner (no unnecessary merge() or whatever) and it only makes sense as a stateful session bean is used to represent conversational state over multiple client calls...by setting an EXTENDED persistence context you recognize that there is a conversation happening.
I'm not seeing when you'd not want to use EXTENDED persistence context (I understand it's not the default persistence context).
Your thoughts please...
Thanks.

For the use-case you mentioned an extended persistence context is a natural fit.
It really depends on whether the semantics of your SFSB operations call for
the references to the same entity objects to be maintained across transactions.
E.g., you might have an SFSB whose state is not derived from persistence state
but which just occasionally makes a database query as part of some of its
business operations. In that case there wouldn't be any reason to use an
extended persistence context.
--ken

How to tell if my phone is locked or not by the ca...

I bought this lumia 920, there are the service carrier apps installed as default.
I want to know if it is locked by the carrier so that I can use other carrier's SIM card.
Phone information:
OS version:8.0.9903.10
Firmware revision number :1232.2109.1242.1002
Hardware revision number:1.0.0.0
Radio software version:1.0.202041.3
Chip SOC version :8960
Mac address:35-C6-038B-70-30
MEID;
IMEI:111111111111
SIM ID: 1111111111111
Nokia enhancements:
Version:1.1.33.5
Detailed here are enchancements from Nokia, designed to fine -tune your Windows Phone experience
Additional info
Manufacturer model name
RM-821-im-mea1-317
Mobiler operator name
000-SA
Configuration ID
97353
The above are the information about my phone
can I tell if it locked , thank you

Hi mate,
Sorry what carrier are you with? You will have to ask them if you are locked to them or not. If you are saying that they have a whole bunch of their apps installed on the phone, my guess is that is locked to them. As I've said though, would pay to check with them, and also when you ask to get it unlocked, try another carrier's SIM card with them and ask about things like if the tethering has been unlocked etc, as carriers can sometimes lock this too, unbeknown to the user.

In the get info screen the HD drive is lock, can not boot the computer

I can not boot my imac. In the Get Info window the Hard Drive has no access marked for everyone and a minus sign on the hard drive. How can I get around this??

Boot into Recovery (command-R at startup), launch Disk Utility, select the startup volume ("Macintosh HD," unless you gave it a different name), and run Repair Permissions (not Repair Disk.) Then reboot as usual. That will undo the worst of the damage. You may need to reinstall some of your third-party software.

I resently updated my phone to new software 8.02 I think, I never had a lock pass code to open my phone. Now I am locked out not knowing the pass code. How do I find that code

I resently updated my phone with the latest software, 8.02 I think. I never had a pass cod before on my phone. Now I am locked out of the phone trying to gyess the 4 digit code. How do I get back in?

Follow this article: iOS: Forgotten passcode or device disabled after entering wrong passcode

AbstractSession.checkAndRefreshInvalidObject(..) not refreshing the passed object

While investigating an issue regarding stale data within optimistic locks (eventually causing an OptimisticLockException) in a setup with two nodes and JMS synchronized caching, I started to debug into EclipseLink and to my understanding found the place where the problem arises but unfortunately I do not quite understand its reason.
Please note: I looked in the forum for a similar question and did not find any, should I have missed one, please feel free to move this topic. Secondly, I am fairly new to EclipseLink, so maybe this question is a no-brainer, unfortunately it is not for me
In org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.cloneAndRegisterObject the object is checked for validity with checkAndRefreshInvalidObject(). The query which is issued eventually after this.executeQuery(query) in checkAndRefreshInvalidObject() returns the correct lock code, but when the control flow returns to cloneAndRegisterObject(), the object "original" still has the old values which are incorporated into "workingClone" a few lines later.
I was a bit surprised to see, that checkAndRefreshObject() has no return value and the object "original" is not updated directly or rather the result of the query within it is simply discarded. I further assume, there should be some behind-the-scenes updating initiated by "query.refreshIdentityMapResult()" in checkAndRefreshObject(), correct?
Environment: EclipseLink 2.6.0, Oracle-DB, Two Payara nodes with a shared cache synchronized by ActiveMQ.
Additional remarks: The table in question uses SINGLE_TABLE inheritance, and the child has a column OPT_LOCK annotated with @Version.
My questions would be:
If checkAndRefreshInvalidObject(original, parentCacheKey, descriptor) is called, where is the actual refresh happening if isConsideredInvalid(..) returns true (which is the case for the scenario being described)?
Should the first parameter of checkAndRefreshInvalidObject(original, parentCacheKey, descriptor) have been updated already after the call to checkAndRefreshInvalidObject()?
If not, how are the refreshed attributes merged into the variable workingClone in org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.class.cloneAndRegisterObject(..), because after checkAndRefreshInvalidObject(..), the method keeps working the the possibly stale "original" or rather creates a "workingClone" of it?
I checked the members "object" on unitOfWorkCacheKey & parentCacheKey in cloneAndRegisterObject(..) and they are both null, should the refresh of checkAndRefreshInvalidObject(..) be visible in these members instead?
The overall logic of cloneAndRegisterObject(..) puzzles me a bit: Even if the results of checkAndRefeshInvalidObject(..) end up in the UOW session, the method keeps working with the old value "original" and does not retrieve it somehow out of the session afterwards. Therefore I suppose, in either UnitOfWorkImpl.populateAndRegisterObject(..) or among the interactions between ObjectLevelReadQuery and ObjectBuilder should be some registration in UOW session happening. Still, even if this were the case, how are these changes incorporated into workingCopy at the end of cloneAndRegisterObject(..)?

tl;dr With UnitOfWorkImpl.checkAndRefreshInvalidObject(original, parentCacheKey, descriptor), where parentCacheKey is the variable used to access the variable original at a later point in ObjectBuilder, is it actually possible to manifest the changes visible on the database directly in the first level cache, and not the second level cache, if the object being updated is the member object of parentCacheKey (which by my current understanding is its second level cache representation)?
After investigating the issue further, I guess I have now some understanding about what is causing the expected behaviour. First I would like to summarize my insights, if anyone notices any fundamental flaws within them, I would appreciate the corrections
Andreas Schmidt wrote on Thu, 06 August 2015 12:22
While investigating an issue regarding stale data within optimistic locks (eventually causing an OptimisticLockException) in a setup with two nodes and JMS synchronized caching, I started to debug into EclipseLink and to my understanding found the place where the problem arises but unfortunately I do not quite understand its reason.
In org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.cloneAndRegisterObject the object is checked for validity with checkAndRefreshInvalidObject(). The query which is issued eventually after this.executeQuery(query) in checkAndRefreshInvalidObject() returns the correct lock code, but when the control flow returns to cloneAndRegisterObject(), the object "original" still has the old values which are incorporated into "workingClone" a few lines later.
I was a bit surprised to see, that checkAndRefreshObject() has no return value and the object "original" is not updated directly or rather the result of the query within it is simply discarded. I further assume, there should be some behind-the-scenes updating initiated by "query.refreshIdentityMapResult()" in checkAndRefreshObject(), correct?
The object is updated in org.eclipse.persistence.internal.descriptors.ObjectBuilder. One possible path is through buildWorkingCopyCloneNormally which later on goes passes through buildObject where the CacheKey of the parent session is retrieved and with it the object reference from checkAndRefreshInvalidObject() which is then updated in buildAttributesIntoObject.
Andreas Schmidt wrote on Thu, 06 August 2015 12:22
Environment: EclipseLink 2.6.0, Oracle-DB, Two Payara nodes with a shared cache synchronized by ActiveMQ.
Additional remarks: The table in question uses SINGLE_TABLE inheritance, and the child has a column OPT_LOCK annotated with @Version.
Two important details missing were
There is an explicit call to flush within the transaction, which according to https://www.eclipse.org/eclipselink/documentation/2.6/concepts/cache003.htm marked it as dirty effectively disabling the second level cache for the remaining transaction.
The cache coordination is set to INVALIDATE_CHANGED_OBJECTS
Andreas Schmidt wrote on Thu, 06 August 2015 12:22
My questions would be:
If checkAndRefreshInvalidObject(original, parentCacheKey, descriptor) is called, where is the actual refresh happening if isConsideredInvalid(..) returns true (which is the case for the scenario being described)?
Should the first parameter of checkAndRefreshInvalidObject(original, parentCacheKey, descriptor) have been updated already after the call to checkAndRefreshInvalidObject()?
If not, how are the refreshed attributes merged into the variable workingClone in org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.class.cloneAndRegisterObject(..), because after checkAndRefreshInvalidObject(..), the method keeps working the the possibly stale "original" or rather creates a "workingClone" of it?
I checked the members "object" on unitOfWorkCacheKey & parentCacheKey in cloneAndRegisterObject(..) and they are both null, should the refresh of checkAndRefreshInvalidObject(..) be visible in these members instead?
The overall logic of cloneAndRegisterObject(..) puzzles me a bit: Even if the results of checkAndRefeshInvalidObject(..) end up in the UOW session, the method keeps working with the old value "original" and does not retrieve it somehow out of the session afterwards. Therefore I suppose, in either UnitOfWorkImpl.populateAndRegisterObject(..) or among the interactions between ObjectLevelReadQuery and ObjectBuilder should be some registration in UOW session happening. Still, even if this were the case, how are these changes incorporated into workingCopy at the end of cloneAndRegisterObject(..)?
In org.eclipse.persistence.internal.descriptors.ObjectBuilder (see above)
Yes
Redundant by the previous answer
I think it should be visible on parentCacheKey but not on unitOfWorkCacheKey, which may be part of the root cause of the issue.
Redundant by previous answers.
While we might be able to circumvent the issue by skipping the intermediate flush, I still think this could be a bug which might be a design issue with the call hierarchy and the parameters of checkAndRefreshInvalidObject(original, parentCacheKey, descriptor) , although I am rather uncertain about the latter, as my experience with EclipseLink is still very limited and I might not see some interdependencies yet
My train of thought is as follows:
If a flush occurs within a transaction, the transaction is marked as dirty and the shared persistence unit cache is ignored and according to https://www.eclipse.org/eclipselink/documentation/2.6/concepts/cache003.htm the objects are built directly in the first level cache, ie. in the unit of work context.
By my understanding, this means, with respect to checkAndRefreshInvalidObject(original, parentCacheKey, descriptor), if the CacheKey has been invalidated, the data should be retrieved from the database but because the transaction is dirty not be written to the second level cache but be created in the first level cache directly.
Within the depths of ObjectBuilder, I think the object original from checkAndRefreshInvalidObject is retrieved to be updated by buildAttributesIntoObject by its CacheKey, in particular the parentCacheKey, for example by
ObjectBuilder:965: cacheKey = session.retrieveCacheKey(primaryKey, concreteDescriptor, joinManager, query);.
My new question are, whether it is actually possible with the current implementation to materialize the fresh data from the database directly in the persistence context cache effectively bypassing the second level cache?
As far as I understood, the CacheKey passed into checkAndRefreshInvalidObject(original, parentCacheKey, descriptor) is the second level cache representation of the object having a reference to it in its member object. If the parentCacheKey has to be used in ObjectBuilder to access and update the object original from checkAndRefreshInvalidObject, will these changes not be visible automatically in the second level cache as well?
The reason, why the update of the variable original was not visible after checkAndRefreshInvalidObject(original, parentCacheKey, descriptor), I think by now was the fact, that the code flow went through ObjectBuilder:2207: workingClone = buildNewInstance(); originating from buildWorkingCopyCloneFromRow due to unitOfWork.wasTransactionBegunPrematurely() being true in buildObjectInUnitOfWork. With workingClone = buildNewInstance(), the updates made by ObjectBuilder:2250: buildAttributesIntoWorkingCopyClone will not affect the object original from checkAndRefreshInvalidObject.
One way to make the changes on the object original is by replacing
ObjectBuilder:2250: workingClone = buildNewInstance()
with
workingClone = unitOfWork.getParentIdentityMapSession(query).retrieveCacheKey(primaryKey, descriptor, joinManager, query).getObject()
but there I definitely lack the experience with the code base to have any clue regarding possible side effects.

How to delete images from folder which are not in the database

I am created windows form
i wont to delete images from the folder where i have stored images but i only want to delete those images which are not in the data base.
i don't know how it is possible . i have written some code
private void button1_Click(object sender, EventArgs e)
string connectionString = "Data Source";
conn = new SqlConnection(connectionString);
DataTable dt = new DataTable();
cmd.Connection = conn;
cmd.CommandText = "select * from tbl_pro";
conn.Open();
SqlDataAdapter da = new SqlDataAdapter(cmd);
da.Fill(dt);
int count = Convert.ToInt32( dt.Rows.Count);
string[] image1 = new string[count];
for (int i = 0; i < count; i++)
image1[i] = dt.Rows[i]["Image1"].ToString();
string[] image2 = new string[count];
for (int i = 0; i < count; i++)
image2[i] = dt.Rows[i]["Image2"].ToString();
var arr = image1.Union(image2).ToArray();
string[] arrays;
String dirPath = "G:\\Proj\\";
arrays = Directory.GetFiles(dirPath, "*", SearchOption.AllDirectories).Select(x => Path.GetFileName(x)).ToArray();
int b= arrays.Count();
for (int j = 1; j <= b; j++)
if (arrays[j].ToString() != arr[j].ToString())
var del = arrays[j].ToString();
else
foreach (var value in del) // ERROR DEL IS NOT IN THE CURRENT CONTEXT
string filePath = "G:\\Projects\\Images\\"+value;
File.Delete(filePath);
here error coming "DEL IS NOT IN THE CURRENT CONTEXT"
I have to change anything .Will It work alright?
pls help me
Sms

Hi Fresherss,
Your del is Local Variable, it can't be accessed out of the if statement. you need to declare it as global variable like below. And if you want to collect the string, you could use the List to collect, not a string. the string will be split to chars
one by one.
List<string> del=new List<string>();
for (int j = 1; j <= b; j++)
if (arrays[j].ToString() != arr[j].ToString())
del.Add(arrays[j].ToString());
else
foreach (var value in del)
string filePath = "G:\\Projects\\Images\\" + value;
File.Delete(filePath);
If you have any other concern regarding this issue, please feel free to let me know.
Best regards,
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Transactions, Persistence Contexts and Entity Managers... Oh My!

Hi
I am just getting into J2EE and EJB3. I have no prior experience with EJB2, we avoided it with our own POJO data access framework. With the advent of EJB3 we would like to use it in a new application.
I am reading the book "Pro EJB 3" by Ketih and Schincariol and am having trouble wrapping my head around then Entity Manager chapter. I don't think it's any fault of the authors, but somehow it's just not coming together in my head. Perhaps it's because I have no real prior EJB experience.
Can anyone point me to a resource that gives an overview of the relationships between Transactions, Persistence Contexts and Entity Managers? Or perhaps I just have to keep mulling it over until it all comes together...?
Thanks in advance!

Hi Shelli,
I haven't read that book but I don't know of a good writeup of the tx topic specifically outside
of the spec itself. There are certainly a lot of combinations, between container-managed
vs. bean-managed EntityManagers, and JTA vs. resource-local. However, the
common usage case within Java EE -- container-managed and JTA -- is very simple.
In this case, the container automatically associates the persistence context with the
active global transaction. If you make a call to another Java EE component within the
same transaction and that component accesses a container-managed EntityManager
for the same persistence unit, the persistence context is automatically propagated so
that both components "see" the same persistence context.
--ken

ASDeploymentException: Could not resolve a persistence unit corresponding

Hi Everyone,
I have been modifying our enterprise application to include 3 .war flies rather than 2 .war files previously. When I deploy the new .ear file, I get the following deployment exception.
I have tried adding the ejb reference for ejb "BiLinkGroupFacade" to the web.xml file for the new .war package, however when I do this I get teh same exception for another ejb in our enterprise app.
Has anyone encountered this problem before?
Thanks very much for your time,
lpg
Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Could not resolve a persistence unit corresponding to the persistence-context-ref-name [ca.avant.amber.bilink.BiLinkGroupFacade/em] in the scope of the module called []. Please verify your application.
at com.sun.enterprise.deployment.BundleDescriptor.findReferencedPUsViaPCRefs(BundleDescriptor.java:702)
at com.sun.enterprise.deployment.EjbBundleDescriptor.findReferencedPUs(EjbBundleDescriptor.java:862)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.getAllPersistenceUnitDescriptors(PersistenceProcessor.java:165)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processApplication(PersistenceProcessor.java:132)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processApplication(DeploymentEventListenerImpl.java:211)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processEvent(DeploymentEventListenerImpl.java:172)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.notifyDeploymentEvent(DeploymentEventListenerImpl.java:122)
at com.sun.enterprise.deployment.backend.DeploymentEventManager.notifyDeploymentEvent(DeploymentEventManager.java:79)
at com.sun.enterprise.deployment.backend.AppDeployer.postDeploy(AppDeployer.java:392)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:251)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:294)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:555)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:564)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:545)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:492)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:267)
at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
;_RequestID=c409950f-6e65-40b8-91dd-35b49289d322;|"DPL8011: autodeployment failure while deploying the application : Could not resolve a persistence unit corresponding to the persistence-context-ref-name [ca.avant.amber.bilink.BiLinkGroupFacade/em] in the scope of the module called []. Please verify your application.
[AutoDeploy] Autodeploy failed : /home/lgrimes/MyRuntimeEnv/lgdomain9.1/autodeploy/amber.ear.

This error deals with EntityManager configuration rather than EJB references. It means you have a @PersistenceContext dependency that cannot be resolved to its corresponding persistence unit. If the unitName attribute is specified, then the deployment code is not finding a persistence unit matching that name. If there's no unitName specified then there are 0 persistence units found.

Deploying application with several web modules having the same context root

Hi,
I would like to be able to deploy an application in Weblogic 12c having one ejb module and several web modules with the same context root. Even though the web modules have the same context root, each of them is deployed to a different virtual host.
Weblogic allows deploying the modules this way as long as their targets are different (i.e. each having a distinct virtual host). However this works only when I don't select a target for the .ear:
Component Type Current Targets
application.ear Enterprise Application (None specified)
application.jar EJB AdminServer
web1.war WEBAPP virtualHost1
web2.war WEBAPP virtualHost2
However if I select as target for the .ear to be AdminServer, the deployment doesn't work anymore, complaining that the context roots are in conflict.
If I remove web2.war from the .ear and deploy the .ear and .jar to AdminServer and web1.war to virtualHost1, the deployment works but the strange thing is that the web application can be accessed also through the AdminServer's main network channel, even though I would expect that it should be accessible only through virtualHost1 network channel. I believe this is the reason why there are context root conflicts when specifying a target for the .ear, because both wars are made accessible to the main network channel.
The reason why I want to keep the wars inside the same .ear is because I want to make them access the application's local EJBs (since as far as I know it's not possible to access a local EJB outside the application even if they belong to the same VM).
Is there a way to deploy the web modules only to the virtual hosts without being targeted to the main network channel?
Regards,
Alexandru

Murphy's Law: If anything can go wrong it will
A corollary to Murphy's law: When everything fails, read the manual.
Web application funda: Every web application must have its own context root. So, if wkfsocos is one
web application then, wkfsocos1 is another web application -
and hence must have its own context root.
Hello Aman,
If you are in E-Commerce version 4.0, then read this
[ISA_Buildtool document |https://service.sap.com/~sapdownload/011000358700001920472003E/ISA_BuildTool_10.pdf]
to create a copy of the application in its own context root.
From your URL pattern I guess you are in E-Commerce version 4.0.
If you are in E-Commerce 5.0 or above, then the
[Extension Guide |http://service.sap.com/~sapdownload/011000358700006120622006E/]gives steps to create a copy with its own context root for use in modification.
(See the chapter on - Creating a project specific Web Application with own context root )
Both these links require access to SAP Service Marketplace. You can also find the
documents through /instguides shortcut in Service Marketplace.
Easwar Ram
http://www.parxlns.com

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

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

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

EJB 3.0 Locking (entity not in the persistence context)

Similar Messages

Maybe you are looking for