JPA Persistence loading issue - JBOSS 5

Hello Every One!!
I have two projects "ProjectA.war" and "ProjectB.war".
In both projects, i am using Oracle 11g, JPA2 with EclipseLink 2.4.2.
and i am using JBOSS 5.1.0 GA application server.
Both have different persistence.xml files with different persistence-unit names, different data-source files.
Here i am connecting same Oracle DB user for both projects.
My Problem is...
First i had deployed ProjectA.war in server. And it is working fine. and DB operations also working fine.
Now i am deploying the ProjectB.war in server besides of ProjectA.war.
So, when i am trying to perform the db operations on ProjectA.war then jboss is searching the POJO classes in ProjectB.war's persistenece.xml file with the help of ProjectB's persistence-unit name.
But actually it need to search in ProjectA.
So, what can i do?
My ProjectA.war Configurations as like below...
============ persistence.xml ==================
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
persistence_2_0.xsd" version="2.0">
          <persistence-unit name="Entity" transaction-type="RESOURCE_LOCAL">
                    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
                    <non-jta-data-source>java:/projectADS</non-jta-data-source>
                    <class>env.model.authorization.IptUsersRoles</class>
                    <class>env.model.defaults.IptUsergroups</class>
                    <class>env.model.defaults.IptUsertype</class>
                    <class>env.model.authorization.IptUsers</class>
                        <properties>
                              <property name="javax.persistence.jdbc.driver"
                                        value="oracle.jdbc.driver.OracleDriver" />
                              <property name="javax.persistence.jdbc.url"
                                        value="jdbc:oracle:thin:@x.x.x.x:1521:TEST" />
                              <property name="javax.persistence.jdbc.user" value="TEST" />
                              <property name="javax.persistence.jdbc.password" value="TEST" />
                              <property name="eclipselink.session.customizer" value="entity.jpa.JPAEclipseLinkSessionCustomizer"/>
                              <property name="eclipselink.logging.level" value="FINEST"/>
                    </properties>
          </persistence-unit>
</persistence>
================= jboss-classloading.xml ===================
<?xml version="1.0" encoding="UTF-8"?>
<classloading xmlns="urn:jboss:classloading:1.0"
                              name="ProjectA.war"
                              domain="DefaultDomain"
                              top-level-classloader="true"
                              parent-domain="Ignored"
            export-all="NON_EMPTY"
            import-all="true"
            parent-first="false">
</classloading>
==================== jboss-web.xml ======================
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
          <resource-ref>
                    <description>DB Connection</description>
                    <res-ref-name>ProjectADS</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <jndi-name>java:/ProjectADS</jndi-name>
                    <res-auth>Container</res-auth>
    </resource-ref>
</jboss-web>
My ProjectB.war Configurations as like below...
============ persistence.xml ==================
<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
    persistence_2_0.xsd" version="2.0">
          <persistence-unit name="IportIBEntity" transaction-type="RESOURCE_LOCAL">
                    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
                    <non-jta-data-source>java:/ProjectBDS</non-jta-data-source>
                    <class>env.model.IptRequestDataRecord</class>
                    <class>env.model.IptResponseDataRecord</class>
                    <properties>
                              <property name="eclipselink.jdbc.driver"
                                        value="oracle.jdbc.driver.OracleDriver" />
                              <property name="eclipselink.jdbc.url"
                                        value="jdbc:oracle:thin:@x.x.x.x:1521:TEST" />
                              <property name="eclipselink.jdbc.user" value="TEST" />
                              <property name="eclipselink.jdbc.password" value="TEST" />
                              <property name="eclipselink.session.customizer"
                                        value="entity.jpa.JPAEclipseLinkSessionCustomizer" />
                              <property name="eclipselink.logging.level" value="FINEST" />
                    </properties>
          </persistence-unit>
</persistence>
================= jboss-classloading.xml ===================
<?xml version="1.0" encoding="UTF-8"?>
<classloading xmlns="urn:jboss:classloading:1.0"
                              name="ProjectB.war"
                              domain="DefaultDomain"
                              top-level-classloader="true"
                              parent-domain="Ignored"
            export-all="NON_EMPTY"
            import-all="true"
            parent-first="false">
</classloading>
==================== jboss-web.xml ======================
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
          <resource-ref>
                    <description>DB Connection</description>
                    <res-ref-name>ProjectBDS</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <jndi-name>java:/ProjectBDS</jndi-name>
                    <res-auth>Container</res-auth>
    </resource-ref>
</jboss-web>
And the console error like below ....
13:26:34,068 INFO [IportIBEntity] finding IptUsers instance with property: userCode, value: ADMIN
13:26:34,709 SEVERE [IportIBEntity] find by property name failed
java.lang.IllegalArgumentException: An exception occurred while creating a query in EntityManager:
Exception Description: Problem compiling [select model from IptUsers model where model.userCode= :propertyValue].
[18, 26] The abstract schema type 'IptUsers' is unknown.
[39, 53] The state field path 'model.userCode' cannot be resolved to a valid type.
          at org.eclipse.persistence.internal.jpa.EntityManagerImpl.createQuery(EntityManagerImpl.java:1512)
          at env.acegi.users.IptUsersDAO.findByProperty(IptUsersDAO.java:174)
          at env.acegi.users.IptUsersDAO.findByUserCode(IptUsersDAO.java:185)
          at env.acegi.security.AcegiAuthentication.loadUserByUsername(AcegiAuthentication.java:51)
          at org.acegisecurity.providers.dao.DaoAuthenticationProvider.retrieveUser(DaoAuthenticationProvider.java:99)
          at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
          at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
          at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
          at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
          at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.ui.logout.LogoutFilter.doFilter(LogoutFilter.java:110)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.concurrent.ConcurrentSessionFilter.doFilter(ConcurrentSessionFilter.java:95)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
          at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
          at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
          at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
          at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
          at java.lang.Thread.run(Thread.java:662)
Caused by: Exception [EclipseLink-0] (Eclipse Persistence Services - 2.4.2.v20130315-93567e3): org.eclipse.persistence.exceptions.JPQLException
Exception Description: Problem compiling [select model from IptUsers model where model.userCode= :propertyValue].
[18, 26] The abstract schema type 'IptUsers' is unknown.
[39, 53] The state field path 'model.userCode' cannot be resolved to a valid type.
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildException(HermesParser.java:150)
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.validate(HermesParser.java:339)
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.populateQueryImp(HermesParser.java:270)
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildQuery(HermesParser.java:157)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:138)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:112)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.<init>(EJBQueryImpl.java:98)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.<init>(EJBQueryImpl.java:82)
          at org.eclipse.persistence.internal.jpa.EntityManagerImpl.createQuery(EntityManagerImpl.java:1510)
          ... 38 more
13:26:34,711 ERROR [[default]] Servlet.service() for servlet default threw exception
java.lang.IllegalArgumentException: An exception occurred while creating a query in EntityManager:
Exception Description: Problem compiling [select model from IptUsers model where model.userCode= :propertyValue].
[18, 26] The abstract schema type 'IptUsers' is unknown.
[39, 53] The state field path 'model.userCode' cannot be resolved to a valid type.
          at org.eclipse.persistence.internal.jpa.EntityManagerImpl.createQuery(EntityManagerImpl.java:1512)
          at env.acegi.users.IptUsersDAO.findByProperty(IptUsersDAO.java:174)
          at env.acegi.users.IptUsersDAO.findByUserCode(IptUsersDAO.java:185)
          at env.acegi.security.AcegiAuthentication.loadUserByUsername(AcegiAuthentication.java:51)
          at org.acegisecurity.providers.dao.DaoAuthenticationProvider.retrieveUser(DaoAuthenticationProvider.java:99)
          at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
          at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
          at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
          at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
          at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.ui.logout.LogoutFilter.doFilter(LogoutFilter.java:110)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.concurrent.ConcurrentSessionFilter.doFilter(ConcurrentSessionFilter.java:95)
          at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
          at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
          at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
          at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
          at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
          at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
          at java.lang.Thread.run(Thread.java:662)
Caused by: Exception [EclipseLink-0] (Eclipse Persistence Services - 2.4.2.v20130315-93567e3): org.eclipse.persistence.exceptions.JPQLException
Exception Description: Problem compiling [select model from IptUsers model where model.userCode= :propertyValue].
[18, 26] The abstract schema type 'IptUsers' is unknown.
[39, 53] The state field path 'model.userCode' cannot be resolved to a valid type.
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildException(HermesParser.java:150)
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.validate(HermesParser.java:339)
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.populateQueryImp(HermesParser.java:270)
          at org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildQuery(HermesParser.java:157)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:138)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:112)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.<init>(EJBQueryImpl.java:98)
          at org.eclipse.persistence.internal.jpa.EJBQueryImpl.<init>(EJBQueryImpl.java:82)
          at org.eclipse.persistence.internal.jpa.EntityManagerImpl.createQuery(EntityManagerImpl.java:1510)
          ... 38 more
In above error description....
"INFO [IportIBEntity] finding IptUsers instance with property: userCode, value: ADMIN"
Here IportIBEntity is the persistence-unit of ProjectB.war, but IptUsers pojo have in ProjectA.war.
So, it is trying to search the POJO in ProjectB.war instead of ProjectA.war
Please help me to solve the problem....

Hello,
More information is required to help you, and as James suggested, the best option would be to move to EclipseLink instead of TopLink Essentials as EclipseLink is actively being developed and is the JPA 2 RI.
Running it on the latest EclipseLink ensures that you are not hitting an issue that has already been fixed, and both are based off TopLink.
Are you deploying an Ear or an exploded directory? If the later, can you try using an Ear?
Best Regards,
Chris

Similar Messages

Experiences on JPA persistence providers other than standard SAP's

Hi developers,
in this thread I would like to gather experiences from all those who have tried using JPA persistence providers other than SAP standard implementation in productive environments
It would be very interesting if you could share you experiences, for instance with regards to:
- advantages of a specific implementation
- disadvantages (if any)
- new features available (e.g. Lazy support for Lob and single-value relationships)
- ease of transport (did you manage to somehow use the java dictionary DCs or what?)
- ease of build (e.g. EclipseLink requires additional build plugins to be developed)
- ease of overall setup: how long did it take to set the DI stuff up (SLD SC creation/track creation/check-in/check-out/activate/transport/...)?
thank you so much for sharing your experiences.
Regards
Vincenzo

Hi Vincenco,
yes, semantic IDs do not have a place in JPA. Semantic keys are needed, but not as IDs.
Both SAP JPA and EclipseLink use @GenerationType.TABLE generation if you define @GenerationType.AUTO. ("AUTO" just means that the persistence provider "should pick an appropriate strategy for the particular database" (javadoc)
Both TABLE and SEQUENCE are somewhat automatic.
I guess the fact of lost-values is because the fetching of IDs is done in another transaction (probably for performance reasons, not to have the sequence table as a bottle neck).
On Oracle, the combination of allocationSize on JPA side and INCREMENT BY / CACHE on Database side is as follows: allocationSize must be equal to INCREMENT BY, but JPA uses the intermediate numbers (which is not the case in normal (PL)SQL programming. There is no annotation-JPA-pendant to CACHE. But that JPA uses the intermediate numbers from memory may be considered as a JPA way of sequence caching (that may be further improved by Sequence CACHE for really big mass insers in one transaction).
CACHE>1 will give you lost values even with allocationSize = Increment BY = 1.
On the other hand, allocationSize=1 may give bad performance on mass inserts because the JPA provider must ask the database for every instance. allocationSize>1 (e.g. 20) is better but will again yield lost values. (But who cares with "long"?)
There is one important issue with both automated value creation strategies - GeneratorType.TABLE and GeneratorType.SEQUENCE: The ID cannot be set by yourself on instantiation of an Entity object. JPA spec defines that the ID is set at the latest on EntityManager.flush or EntityManager.commit, which is sometimes too late if you have container managed transaction boundaries.
But both SAP JPA and EclipseLink assure that the ID with Table and Sequence is set already after call EntityManager.persist(newObject). This improves a lot, but may be not enough.
Example:
@Entity(name="T_ORDER")
public class Order {
     @OneToMany(targetEntity=OrderItem.class, mappedBy="order", cascade=CascadeType.ALL)
     private List<OrderItem> items = new ArrayList<OrderItem>();
     public void addItem (OrderItem item) {
          this.items.add(item);
          item.setOrder(this);
@Entity(name="T_ORDERITEM")
public class OrderItem {
     @ManyToOne(targetEntity = Order.class)
     private Order order;
EntityManager em = emf.createEntityManager();
em.getTransaction().begin();
Order o = new Order();
OrderItem i1 = new OrderItem();
o.addItem(i1);
em.persist(o);
OrderItem i2 = new OrderItem();
o.addItem(i2);
At the end of this snippet, o and i1 have ID != null but i2 has ID==null. there is no way to "auto-persist" an object which gets into a relation to an already persisted object. i2 gets an ID!= null after flush or commit.
This may be tricky if your business logic that adds items is "pojo" without acces to EntityManager or if you do not want to mess up your business logic with flushes.
How to "broadcast" the unique IDs of just inserted order items to the User Interface if they are not yet set in the last line of your SLSB?
We switched to simple UUIDs that are generated on instanciation. long VARCHAR2s, but it works fine and is very common.
Regards
-Rolf

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Report loading Issue

Hello all,
I am using Oracle 6i for report and oracle10g for the database.I have created a matrix report in oracle Report but which report taking so much time to show the output it almost taking more than 10 minutes,at the same time that query executed within 1 minute in toad which used in matrix report.
kindly guide me how to solve the loading issue.

I did not used any formula column in my report,all the values are taking from query.
But I used different types of format trigger in my report for the coloring purpose.Does it make any problem?

Data Load Issue "Request is in obsolete version of DataSource"

Hello,
I am getting a very strange data load issue in production, I am able to load the data upto PSA, but when I am running the DTP to load the data into 0EMPLOYEE ( Master data Object) getting bellow msg
Request REQU_1IGEUD6M8EZH8V65JTENZGQHD not extracted; request is in obsolete version of DataSource
The request REQU_1IGEUD6M8EZH8V65JTENZGQHD was loaded into the PSA table when the DataSource had a different structure to the current one. Incompatible changes have been made to the DataSource since then and the request cannot be extracted with the DTP anymore.
I have taken the follwoing action
1. Replicated the data source
2. Deleted all request from PSA
2. Activated the data source using (RSDS_DATASOURCE_ACTIVATE_ALL)
3. Re transported the datasource , transformation, DTP
Still getting the same issue
If you have any idea please reply asap.
Samit

Hi
Generate your datasource in R/3 then replicate and activate the transfer rules.
Regards,
Chandu.

Index.php loading issue

I finished and uploaded a new site in .php.
I have a graphics loading issue only with IE.
The js accordion with images will not reload after returning to the home page.
Anyone out thier that can shed some light on this?
http://carpetcleaningsantabarbarapro.com/index.php
Thank you in advance
Crissymarie

Ken might be on to something. The current release of jQuery is 1.7.2 which is compatible with jQuery Cycle.
For the latest core library, you can link to jQuery's CDN like so:
<script type="text/javascript" src="http://code.jquery.com/jquery-latest.min.js"></script>
You have some improperly nested <h3> tags around your lists on lines 170 and 191. To keep your code error free, simply delete the heading tags.
Finally, as a courtesy to your site visitors, consider adding a cookie so people don't have to watch the Flash Spokesperson every time they go to your home page. The link below shows how:
http://alt-web.com/DEMOS/cookie-test-show-hide-flash-intro.shtml
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/

TileList data load issue

I am having an issue where the data that drives a tilelist
works correctly when the tile list is not loaded on the first page
of the application. When it is put on a second page in a viewstack
then the tilelist displays correctly when you navigate to it. When
the tilelist is placed in the first page of the application I get
the correct number of items to display in the tilelist but the
information the item renderer is supposed to display, ie a picture,
caption and title, does not. The strange thing is that a Tree
populates correctly given the same situation. Here is the sequence
of events:
// get tree is that data for the tree and get groups is the
data for the tilelist
creationComplete="get_tree.send();get_groups.send();"
<mx:HTTPService showBusyCursor="true" id="get_groups"
url="[some xml doc]" resultFormat="e4x"/>
<mx:XMLListCollection id="myXMlist"
source="{get_groups.lastResult.groups}"/>
<mx:HTTPService showBusyCursor="true" id="get_tree"
url="[some xml doc]" resultFormat="e4x" />
<mx:XMLListCollection id="myTreeXMlist"
source="{get_tree.lastResult.groups}"/>
And then the data provider of the tilelist and tree are set
accordingly. I tried putting moving the data calls from the
creation complete to the initialize event thinking that it would
hit earlier in the process and be done by the time the final
completion came about but that didn't help either. I guess I'm just
at a loss as to why the tree works fine no matter where I put it
but the TileList does not. It's almost like the tree and the
tilelist will sit and wait for the data but the item renderer in
the tilelist will not wait. Which would explain why clicking on the
tile list still produces the correct sequence of events but the
visual component of the tilelist is just not working right. Anyone
have any ideas?

Ok, so if ASO value is wrong, then its a data load issue and no point messing around with the BSO app. You are loading two transactions to the exact same intersection. Make sure your data load is set to aggregate values and not overwrite.

BI Load issue in the transformation/DTP after SP 17

Hello,
After SP 17 applied in our BI system, we are having load issue in one particular transformation/DTP.
See below the errors:
u2022 Messages for 101 data records saved; request is red acc. to
configuration
u2022 Thee is no active nametab in the system, although an active ABAP/4
Dictionary object was expected. Reactivate the ABAP/4 Dictionary object.
Also I have activated the DSO, transformation and DTP. Also I went to SE14 and try to adjust my DSO, SE11 and activate the table but still having the issue.
Can someone advise me on how to resolve this issue?
Thanks a lot.
Cesar

Hi,
Do the following: In BI, run transaction SE38 >> RSDG_CUBE_ACTIVATE to recreate the Metadata information
for the Info-provider.
Then execute another program via SE38: RSDD_RSTMPLWIDTP_GEN_ALL
See Note 1161940 and 1152453 for more details.
Regards,

BW sales load issue

I have a problem with this. The jobs in the screen snapshot below are running too long - 2LIS_11_VAITM, 2LIS_11_V_ITM, and 2LIS_13_VDITM. They use to run for just a couple of minutes. The job configuration is; when the first job finishes a delay of 10 minutes will be incurred then the second job will run, then another 10 minute delay before the third job runs. After these 3 jobs are complete an activation job needs to run. This activation job began to fail because the first 3 jobs were not finished. For now, the activation job has been moved but we need to understand why these are running longer and fix it. We may be experiencing a problem with database performance in PDF but I would not think it would take that much longer.
This is the BW sales load issue
The info-package group is schedule @ 00:05 am and it contains 3 info-packages: VAITM, V_ITM and VDITM with 10 minutes execution gap.
The first VAITM started 00:05:46 and ended it up in BW at 00:09:02.
Then we have 10 minutes delayed between jobs.
V_ITM started 00:20:12 and for some reason it finished at 01:00:51. We can see communication between PDF and BWP took much longer than normal.
Then we have 10 minutes delayed between jobs
At 01:00:25 the activation job started and failed. It requires the info-packages to be in GREEN status but V_ITM finished @ 01:00:51.
It probably failed because V_ITM still had YELLOW status at the moment.
VDITM started 01:12:02 and finally finished it load at 02:09:16. A big communication delayed between system.
See below an example of the load on the 01/14/2007. It looks normal communication between systems
Could you please give solution for this.
Thanks
Vasu.

Hi,
For every job you define and at the same time, you can also define the priority
levels to each job, since, during your job execution might be your job queue is
full with some other background processings, so try setting up the priority levels
of the job.
cheers,
Pattan.

Does resteasy API have class loader issues when using via OSGi

Does resteasy API have class loader issues when using via OSGi

Hi Scott,
THis isnt an answer to ur Question, but could u tell me which jar files are needed for the packages:
com.sap.portal.pcm.system.ISystems
com.sap.portal.pcm.system.ISystem
and under which path I coul dfind them.
Thnx
Regards
Meesum.

Demantra Data Load Issue

I am new to Demantra. Have installed a stand alone Demantra system in our server. In order to load data, I created a new model, defined item and location levels, then clicked on 'Build Model'. The data is loaded into 3 custom tables created by me. After creating the model, I cannot login to 'Collaborator Workbench', it gives message 'There are system errors. Please contact your System Administrator'. Can anyone please tell me what I am doing wrong and how to resolve the issue.
Thanks

Ok, so if ASO value is wrong, then its a data load issue and no point messing around with the BSO app. You are loading two transactions to the exact same intersection. Make sure your data load is set to aggregate values and not overwrite.

Integrated WL/Jdeveloper class loading issue

Hello,
I am trying to run a deployed project , getting into this class loading issue. Any idea?
javax.security.auth.login.LoginException: java.lang.LinkageError: loader constraint violation: when resolving interface method "com.scat.util.identity.UserFactory.lookup(Ljava/lang/String;)Lcom/scat/domain/identity/User;" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, com/scat/auth/authentication/login/UserLoginModule, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/scatl/util/identity/UserFactory, have different Class objects for the type com/scat/domain/identity/User used in the signature
Thanks
Ram

How many times are you loading the com/scat/domain/identity/User type?
Is this in the system classloader and the application? and are you using class loading filtering in the application, for example,
in weblogic.xml - prefer-web-inf-classes?

EclipseLink persistence provider issue with weblogic 10.3

Hi All,
I have been trying to deploy and run an EAR in weblogic but when I run the application I get the following warning: WARNING: Found unrecognized persistence provider "org.eclipse.persistence.jpa.PersistenceProvider" in place of OpenJPA provider. This provider's properties will not be used.
The following is my persistence.xml:
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence persistence_1_0.xsd" version="1.0">
<persistence-unit name="default" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>DataSourceName</jta-data-source>
<class>oracle.communications.platform.entity.impl.CharacteristicSpecificationDAO</class>
<properties>
<property name="eclipselink.logging.level" value="FINEST" />
<property name="eclipselink.target-database" value="org.eclipse.persistence.platform.database.oracle.OraclePlatform" />
<property name="eclipselink.target-server" value="WebLogic_10" />
<property name="eclipselink.session-event-listener" value="oracle.communications.platform.persistence.impl.PomsSessionEventListener" />
<property name="eclipselink.session.customizer" value="oracle.communications.platform.util.EclipseLinkSessionCustomizer" />
<property name="poms.cache.coordination.implementation" value="jms" />
<property name="poms.cache.coordination.ipaddress" value="10.178.139.64" />
<property name="poms.cache.coordination.port" value="7101" />
<property name="poms.cache.coordination.multicast.group.address" value="226.10.12.64" />
<property name="poms.cache.coordination.multicast.port" value="3121" />
<property name="poms.cache.coordination.topic.connection.factory.name" value="EclipseLinkTopicConnectionFactory" />
<property name="poms.cache.coordination.topic.name" value="EclipseLinkTopic" />
<property name="poms.cache.coordination.username" value="weblogic" />
<property name="poms.cache.coordination.password" value="weblogic" />
<property name="poms.cache.coordination.password.encrypted" value="false" />
</properties>
</persistence-unit>
</persistence>
I have written a session customizer that reads properties from the persistence.xml and initializes stuff. But because of the warning i mentioned earlier... I am getting null for all property entries.
I moved the eclipselink jar entry up ahead of openjpa jar entry in weblogic.server.modules_10.3.1.0.xml and refcount.xml in /modules/features directory. I am still getting the same problem.
I read in many posts for workarounds for this issue but didnt find anything which worked for me. I would be grateful if someone could provide me a hint as to how to make it work.
Thanks in advance,
Prashanth.

Prashanth,
Hi, there should be no issue running EclipseLink on WebLogic while you see this warning. If you are getting null properties it may be the result of another issue, could you post specific exceptions and the part of your client code that is having a problem.
1) The warning below normally appears only when running your persistence unit with an "application managed" JTA datasource as opposed to a "globally defined server scoped datasource". Even then it can be ignored as there are still parts of WebLogic that depend on OpenJPA. Even though the warning states that properties are ignored - they are not and you should see your persistence unit loaded properly.
I encountered this issue when running an "application managed" JTA - here is an extract of the log showing the warning and the full functioning of the pu later - the persistence unit and example code can be found on the weblogic tutorial examples link below
"[EL Finer]: 2008.10.29 13:03:55.565--ClientSession(30346337)--Thread(Thread[[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--client released
WARNING: Found unrecognized persistence provider "org.eclipse.persistence.jpa.PersistenceProvider" in place of OpenJPA provider. This provider's properties will not be used.
[EL Info]: 2008.10.29 13:03:56.079--ServerSession(14772987)--EclipseLink, version: Eclipse Persistence Services - 1.1.0 (Build 20081023)
[EL Info]: 2008.10.29 13:03:56.391--ServerSession(14772987)--file:/C:/view_w34r1a/examples/org.eclipse.persistence.example.jpa.server.weblogic.enterpriseEJB/build/classes/-exampleLocal login successful
15 Entities in storage: 15
[EL ExampleLocal EM]: enterprise: Object: [email protected]( id: 6 state: null parent: HashSet@15794734 references: HashSet@15794734)
[EL ExampleLocal EM]: enterprise: Object: [email protected]( id: 26 state: null parent: HashSet@8800655 references: HashSet@8800655)
I raised the following minor issue with our WebLogic Server team in Oct for reference - however this warning did not affect proper functioning of EclipseLink JPA.
https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=7520161
You may reference the following tutorial on running EclipseLink JPA on WebLogic 10.3, it details all the steps necessary to get a JTA container managed persistence unit running via a stateless session bean and a servlet client. It also details and links to application managed datasource configuration details.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
2) eclipselink.jar location in WebLogic?
The eclipselink.jar library should stay in the modules or patch_* directory depending on whether you are running a standalone WebLogic server or as part of a Fusion Middleware JDeveloper environment.
See the following link that details deployment options for WebLogic and EclipseLink
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#EclipseLink_JAR_location
Note: I have not modified the load order of EclipseLink, OpenJPA or Kodo, I am running all including this version of OpenJPA in my modules directory. [org.apache.openjpa_1.0.0.0_1-1-1-SNAPSHOT.jar]
3) I noticed that you are defining the target-database property in your persistence unti but you are running as JTA not RESOURCE_LOCAL. This property can be removed if your JTA datasource is defined as a Transactional server scoped datasource via the WebLogic console.
thank you
/michael
http://www.eclipselink.org

JPA - lazy loading for LOB field

Hi all,
JPA 1.0 specification mandates that all JPA-compliant implementation support lazy loading for certain kind of entity field.
For LOB fields lazy loading is OPTIONAL.
I am experiencing odd runtime behaviors on my custom software which would point to this feature not being supported.
Can anyone please tell me if SAP JPA 1.0 implementation on NW CE 711 implements this feature or not?
Thanks in advance
Regards
Vincenzo

Hi Vincenco,
I am sure that this is the same as with single-valued relationships (@OneToOne, @ManyToOne): Lazy loading would require bytecode manipulation/generation, so SAP JPA does not support it in 7.20 (and of course not in 7.11)
See tulsi jiddimani's elaborate answer here: Re: JPA: Documentation on LazyLoad.
In 7.30 enhancements, you really can find lazy loading support for single-valued relationships with getReference.
http://help.sap.com/saphelp_nw73/helpdata/en/68/f676ef36094f4381467a308a98fd2a/content.htm
but @Lob and @Basic is not mentioned.
If you need lazy loading in 7.11, you have two alternatives:
1. Put the Lob fields into separate entities, work around the missing feature in SAP JPA with ugly @OneToMany - Relations
2. Use another persistence provider like EclipseLink, read Sabine Heider's blogs about integrattion of EclipseLink in SAP NetWeaver and static bytecode weaving for lazy loading. /people/sabine.heider/blog
Regards
Rolf

JSP loading issue: HTTP 404 error

I have a JSP page that stopped loading up.
It gives me the Apache HTTP 404 error that it can not find the JSP page.
There are no servlet classes associated with the JSP page.
Simply, it is an HTML page calling a JSP page.
This issue appeared after we(IT team) incorporated servlets on the machine.
Directory structure changed, but it shouldn't have effected our JSP pages.
Directory structure
../wwwroot/Finance/Labor.html goes to ../wwwroot/Finance/Labor.jsp

And how does the HTML page invoke the JSP page?
Are you doing it via a <form> or are you linking to it through an <a href>?
You really didn't provide very much information. There are a lot of things that could go wrong. For example, Tomcat generally likes its JSPs to be in a specific place which is NOT the default Apache document root. You'd explicitly have to configure Tomcat to use the same Apache document root though.
Similarly, application specific Servlets are usually in a sub-directory of the one containing JSP files for that application. In other words, you don't really put JSPs in c:/JSPs on one machine, HTML in /home/rycherX/www on another machine and Servlets in \\rycherX\workspace\Servlets on a third.
The first place to start is to tell us what Servlet Engine you just installed. Tomcat? JBoss? WebSphere?

JPA Persistence loading issue - JBOSS 5

Similar Messages

Maybe you are looking for