EclipseLink on WebLogic

As promissed in this thread No insert, update, delete using TopLink Essentials on Weblogic I have tested EclipseLink on WebLogic and it runs without any problems.
I have used the following persistence.xml
<?xml version="1.0" encoding="windows-1252" ?>
<persistence xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
version="1.0" xmlns="http://java.sun.com/xml/ns/persistence">
<persistence-unit name="VoorbeeldEJB">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>ejbDS</jta-data-source>
<class>datamodel.persistence.Department</class>
<class>datamodel.persistence.Employee</class>
<properties>
<property name="eclipselink.logging.level" value="FINEST"/>
<property name="eclipselink.target-database" value="Oracle"/>
<property name="eclipselink.cache.shared.default" value="false"/>
<property name="eclipselink.target-server" value="WebLogic_10"/>

</properties>
</persistence-unit>
</persistence>
The version of WebLogic used is the one which is provided with JDeveloper 11.
Reference to the above mentioned thread for TopLink Essentials on WebLogic.

Rene,
Thank you for verifying this EclipseLink in WebLogic 10.3 functionality and getting back to us on your application configuration.
/michael att eclipselink.org
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial

Similar Messages

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

ClassNotFound Exception integrating Coherence and Eclipselink with composite key entity objects

I am hooking up coherence as an L2 cache for eclipselink in weblogic 12c (using the latest released weblogic and eclipselink 2.4.2.v20130514-5956486). I have my application war and coherence gar packaged in the same EAR file. For Entity Objects with single primary keys (Longs) coherence integration works as expected. However I have several multi-part key Entity Objects that use an IdClass to represent the key. When these objects get serialized, coherence throws a class not found exception. I'm assuming its because the cachekey used is an instance of my applications IdClass, and the weblogic classloader doesn't have access to this. Since eclipselink hides the cache integration with coherence, I cannot pass my classloader off to coherence (as i do with other caches i'm using directly with coherence).
How can I get around this problem?
I saw this option in ExternalizableHelper.xml, but modifying it directly had no effect:


<force-classloader-resolving>false</force-classloader-resolving>
Here is the stack trace:
ClassLoader: null) java.io.IOException: readObject failed: java.lang.ClassNotFoundException: com.oracle.pgbu.common.data.OverlayIdClass
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:623)
at weblogic.coherence.service.internal.io.WLSObjectInputStream.resolveClass(WLSObjectInputStream.java:45)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at com.tangosol.util.ExternalizableHelper.readSerializable(ExternalizableHelper.java:2262)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2393)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2315)
at oracle.eclipselink.coherence.integrated.internal.cache.RelationshipUpdateProcessor.readExternal(RelationshipUpdateProcessor.java:82)
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:2086)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2390)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at oracle.eclipselink.coherence.integrated.cache.WrapperSerializer.deserialize(WrapperSerializer.java:79)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2791)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
ClassLoader: null
at com.tangosol.util.Base.ensureRuntimeException(Base.java:286)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.tagException(Grid.CDB:50)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onInvokeRequest(PartitionedCache.CDB:61)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$InvokeRequest.run(PartitionedCache.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool.add(DaemonPool.CDB:20)
at com.tangosol.coherence.component.util.DaemonPool.add(DaemonPool.CDB:1)
at com.tangosol.coherence.component.net.message.requestMessage.DistributedCacheKeyRequest.onReceived(DistributedCacheKeyRequest.CDB:2)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:23)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:51)
at java.lang.Thread.run(Thread.java:724)
Caused by: java.io.IOException: readObject failed: java.lang.ClassNotFoundException: com.oracle.pgbu.common.data.OverlayIdClass
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:623)
at weblogic.coherence.service.internal.io.WLSObjectInputStream.resolveClass(WLSObjectInputStream.java:45)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at com.tangosol.util.ExternalizableHelper.readSerializable(ExternalizableHelper.java:2262)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2393)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2315)
at oracle.eclipselink.coherence.integrated.internal.cache.RelationshipUpdateProcessor.readExternal(RelationshipUpdateProcessor.java:82)
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:2086)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2390)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at oracle.eclipselink.coherence.integrated.cache.WrapperSerializer.deserialize(WrapperSerializer.java:79)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2791)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
ClassLoader: null
at com.tangosol.util.ExternalizableHelper.readSerializable(ExternalizableHelper.java:2270)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2393)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2315)
at oracle.eclipselink.coherence.integrated.internal.cache.RelationshipUpdateProcessor.readExternal(RelationshipUpdateProcessor.java:82)
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:2086)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2390)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at oracle.eclipselink.coherence.integrated.cache.WrapperSerializer.deserialize(WrapperSerializer.java:79)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2791)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$InvokeRequest.deserializeProcessor(PartitionedCache.CDB:7)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onInvokeRequest(PartitionedCache.CDB:37)
... 10 more

I am hooking up coherence as an L2 cache for eclipselink in weblogic 12c (using the latest released weblogic and eclipselink 2.4.2.v20130514-5956486). I have my application war and coherence gar packaged in the same EAR file. For Entity Objects with single primary keys (Longs) coherence integration works as expected. However I have several multi-part key Entity Objects that use an IdClass to represent the key. When these objects get serialized, coherence throws a class not found exception. I'm assuming its because the cachekey used is an instance of my applications IdClass, and the weblogic classloader doesn't have access to this. Since eclipselink hides the cache integration with coherence, I cannot pass my classloader off to coherence (as i do with other caches i'm using directly with coherence).
How can I get around this problem?
I saw this option in ExternalizableHelper.xml, but modifying it directly had no effect:


<force-classloader-resolving>false</force-classloader-resolving>
Here is the stack trace:
ClassLoader: null) java.io.IOException: readObject failed: java.lang.ClassNotFoundException: com.oracle.pgbu.common.data.OverlayIdClass
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:623)
at weblogic.coherence.service.internal.io.WLSObjectInputStream.resolveClass(WLSObjectInputStream.java:45)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at com.tangosol.util.ExternalizableHelper.readSerializable(ExternalizableHelper.java:2262)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2393)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2315)
at oracle.eclipselink.coherence.integrated.internal.cache.RelationshipUpdateProcessor.readExternal(RelationshipUpdateProcessor.java:82)
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:2086)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2390)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at oracle.eclipselink.coherence.integrated.cache.WrapperSerializer.deserialize(WrapperSerializer.java:79)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2791)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
ClassLoader: null
at com.tangosol.util.Base.ensureRuntimeException(Base.java:286)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.tagException(Grid.CDB:50)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onInvokeRequest(PartitionedCache.CDB:61)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$InvokeRequest.run(PartitionedCache.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool.add(DaemonPool.CDB:20)
at com.tangosol.coherence.component.util.DaemonPool.add(DaemonPool.CDB:1)
at com.tangosol.coherence.component.net.message.requestMessage.DistributedCacheKeyRequest.onReceived(DistributedCacheKeyRequest.CDB:2)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:23)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:51)
at java.lang.Thread.run(Thread.java:724)
Caused by: java.io.IOException: readObject failed: java.lang.ClassNotFoundException: com.oracle.pgbu.common.data.OverlayIdClass
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:623)
at weblogic.coherence.service.internal.io.WLSObjectInputStream.resolveClass(WLSObjectInputStream.java:45)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at com.tangosol.util.ExternalizableHelper.readSerializable(ExternalizableHelper.java:2262)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2393)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2315)
at oracle.eclipselink.coherence.integrated.internal.cache.RelationshipUpdateProcessor.readExternal(RelationshipUpdateProcessor.java:82)
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:2086)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2390)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at oracle.eclipselink.coherence.integrated.cache.WrapperSerializer.deserialize(WrapperSerializer.java:79)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2791)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
ClassLoader: null
at com.tangosol.util.ExternalizableHelper.readSerializable(ExternalizableHelper.java:2270)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2393)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2315)
at oracle.eclipselink.coherence.integrated.internal.cache.RelationshipUpdateProcessor.readExternal(RelationshipUpdateProcessor.java:82)
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:2086)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2390)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2336)
at oracle.eclipselink.coherence.integrated.cache.WrapperSerializer.deserialize(WrapperSerializer.java:79)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2791)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$InvokeRequest.deserializeProcessor(PartitionedCache.CDB:7)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onInvokeRequest(PartitionedCache.CDB:37)
... 10 more

OEPE 1.6 - Oracle WebLogic Server 11gR1 PatchSet 3 requres WLS 10.3.4

Hi!
Anyone knowing when Weblogic Server 10.3.4 is planed GA
Borre

Borre,
See the recent OTN post from 20110115 detailing the latest release of Oracle WebLogic Server and some retesting of the previous issues related to JSR-317 JPA 2.0 support below.
Re: Deploy Hibernate based EAR file on Weblogic 10.3.3?
The latest release of Oracle WebLogic Server has been available on OTN at the following location since 20110115.
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
This release provides support for JSR-317 JPA 2.0 container managed applications using the QWG8 patch or a manual prepending classpath change.
In 10.3.3.0 you were required to use the FilteringClassLoader via the *<wls:prefer-application-packages>* addition to your application managed persistence unit - this workaround as well as the persistence.xml renaming one is now fully deprecated and not required in 10.3.4.0 for both application and container managed persistence contexts.
As of 20110115 the 5 outstanding issues below look to be fixed by applying the http://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309 patch for QWG8 or manually prepending to the WebLogic 10.3.4.0 server classpath.
commEnv.cmd: line 67
@rem Set BEA Home
set BEA_HOME=C:\opt\wls1034r20110115
@rem Enable JPA 2.0 functionality on WebLogic Server 10.3.4 with the following patch line for commEnv.cmd:67
set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.0.0.0_2-0-0.jar;%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-0.jar
A JPA 2.0 EE application using EclipseLink as the JPA2 persistence provider on WebLogic is detailed in the analysis section below1) JPA 2.0 XSD parsing - verified
2) New JPA 2.0 schema elements like <shared-cache-mode>NONE</shared-cache-mode> - verified
3) JPA 2.0 runtime API like a entityManager.getMetamodel(); call on the Servlet or Stateless session bean - verified
4) JPA 2.0 weaving/instrumentation - this will require a more detailed lazy model and more debugging to fully verify
5) Dependency Injection of a container managed JPA 2.0 entityManager on a EJB component like a stateless session bean - verified
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
OTN downloadhttp://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
Patching
http://download.oracle.com/docs/cd/E18476_01/doc.220/e18480/weblogicchap.htm
Documentationhttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13852/toc.htm
Supported Oracle WebLogic Server Versionshttp://download.oracle.com/docs/cd/E15315_06/help/oracle.eclipse.tools.weblogic.doc/html/SupportedServerVersions.html
TopLink JPA 2.0 Specific documentation/patchinghttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309
EclipseLink Wiki: JPA 2.0 using EclipseLink on WebLogic analysis (XSD, Weaving, DI of @PersistenceContext)http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
thank you
/Michael O'Brien
http://www.eclipselink.org

WebLogic 10.0 + JPA 2.0 = errors

Hi,
Is there a known way to add support for JPA 2.0 in Weblogic 10.0?
Thanks.

See the recent OTN post from 20110115 detailing the latest release of Oracle WebLogic Server and some retesting of the previous issues related to JSR-317 JPA 2.0 support below.
Re: Deploy Hibernate based EAR file on Weblogic 10.3.3?
The latest release of Oracle WebLogic Server has been available on OTN at the following location since 20110115.
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
This release provides support for JSR-317 JPA 2.0 container managed applications using the QWG8 patch or a manual prepending classpath change.
In 10.3.3.0 you were required to use the FilteringClassLoader via the *<wls:prefer-application-packages>* addition to your application managed persistence unit - this workaround as well as the persistence.xml renaming one is now fully deprecated and not required in 10.3.4.0 for both application and container managed persistence contexts.
As of 20110115 the 5 outstanding issues below look to be fixed by applying the http://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309 patch for QWG8 or manually prepending to the WebLogic 10.3.4.0 server classpath.
commEnv.cmd: line 67
@rem Set BEA Home
set BEA_HOME=C:\opt\wls1034r20110115
@rem Enable JPA 2.0 functionality on WebLogic Server 10.3.4 with the following patch line for commEnv.cmd:67
set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.0.0.0_2-0-0.jar;%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-0.jar
A JPA 2.0 EE application using EclipseLink as the JPA2 persistence provider on WebLogic is detailed in the analysis section below1) JPA 2.0 XSD parsing - verified
2) New JPA 2.0 schema elements like <shared-cache-mode>NONE</shared-cache-mode> - verified
3) JPA 2.0 runtime API like a entityManager.getMetamodel(); call on the Servlet or Stateless session bean - verified
4) JPA 2.0 weaving/instrumentation - this will require a more detailed lazy model and more debugging to fully verify
5) Dependency Injection of a container managed JPA 2.0 entityManager on a EJB component like a stateless session bean - verified
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
OTN downloadhttp://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
Patching
http://download.oracle.com/docs/cd/E18476_01/doc.220/e18480/weblogicchap.htm
Documentationhttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13852/toc.htm
Supported Oracle WebLogic Server Versionshttp://download.oracle.com/docs/cd/E15315_06/help/oracle.eclipse.tools.weblogic.doc/html/SupportedServerVersions.html
TopLink JPA 2.0 Specific documentation/patchinghttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309
EclipseLink Wiki: JPA 2.0 using EclipseLink on WebLogic analysis (XSD, Weaving, DI of @PersistenceContext)http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
thank you
/Michael O'Brien
http://www.eclipselink.org

TopLink on WebLogic or oracle.toplink.PersistenceProvider

Hy.
I have applied patch 5KXF to add toplink 11g on WebLogic 10.3.
Now, in BEA_HOME\patch_wls1030\patch_jars\ there is toplink.jar.
But how can I use it?
Inside toplink.jar there is file META-INF\services\META-INF\services\javax.persistence.spi.PersistenceProvider.
I assume that content of this file is the name of the implementation class.
It is "oracle.toplink.PersistenceProvider".
But when I put this name in persistence.xml and try to deploy my EAR, this message appears
=====================================================================================================
weblogic.deployment.EnvironmentException: Error processing persitence unit toplink of module toplink.jar: Error instantiating the Persistenc
e Provider class oracle.toplink.essentials.PersistenceProvider of the PersistenceUnit toplink: java.lang.ClassNotFoundException: oracle.topl
ink.essentials.PersistenceProvider
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:322)
at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123)
at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331)
at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245)
at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63)
=====================================================================================================
The persistence.xml file looks like
=====================================================================================================
<persistence-unit name="toplink">
<provider>
oracle.toplink.essentials.PersistenceProvider
</provider>
<jta-data-source>jdbc/miroslav_rehirDS</jta-data-source>
</persistence-unit>
=====================================================================================================
One thing more .... In the filesistem I can't find class oracle.toplink.PersistenceProvider.
On the other hand it is OK to put
<provider>
org.eclipse.persistence.jpa.PersistenceProvider
</provider>
Thanks four your replies,
Miroslav

Miroslav,
You may be interested in the latest release of Oracle WebLogic Server.
See the recent OTN post from 20110115 detailing the latest release of Oracle WebLogic Server and some retesting of the previous issues related to JSR-317 JPA 2.0 support below.
11g Release 1 Patch Set 3 (WLS 10.3.4)
The latest release of Oracle WebLogic Server has been available on OTN at the following location since 20110115.
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
This release provides support for JSR-317 JPA 2.0 container managed applications using the QWG8 patch or a manual prepending classpath change.
In 10.3.3.0 you were required to use the FilteringClassLoader via the *<wls:prefer-application-packages>* addition to your application managed persistence unit - this workaround as well as the persistence.xml renaming one is now fully deprecated and not required in 10.3.4.0 for both application and container managed persistence contexts.
As of 20110115 the 5 outstanding issues below look to be fixed by applying the http://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309 patch for QWG8 or manually prepending to the WebLogic 10.3.4.0 server classpath.
commEnv.cmd: line 67
@rem Set BEA Home
set BEA_HOME=C:\opt\wls1034r20110115
@rem Enable JPA 2.0 functionality on WebLogic Server 10.3.4 with the following patch line for commEnv.cmd:67
set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.0.0.0_2-0-0.jar;%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-0.jar
A JPA 2.0 EE application using EclipseLink as the JPA2 persistence provider on WebLogic is detailed in the analysis section below1) JPA 2.0 XSD parsing - verified
2) New JPA 2.0 schema elements like <shared-cache-mode>NONE</shared-cache-mode> - verified
3) JPA 2.0 runtime API like a entityManager.getMetamodel(); call on the Servlet or Stateless session bean - verified
4) JPA 2.0 weaving/instrumentation - this will require a more detailed lazy model and more debugging to fully verify
5) Dependency Injection of a container managed JPA 2.0 entityManager on a EJB component like a stateless session bean - verified
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
OTN downloadhttp://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
Patching
http://download.oracle.com/docs/cd/E18476_01/doc.220/e18480/weblogicchap.htm
Documentationhttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13852/toc.htm
Supported Oracle WebLogic Server Versionshttp://download.oracle.com/docs/cd/E15315_06/help/oracle.eclipse.tools.weblogic.doc/html/SupportedServerVersions.html
TopLink JPA 2.0 Specific documentation/patchinghttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309
EclipseLink Wiki: JPA 2.0 using EclipseLink on WebLogic analysis (XSD, Weaving, DI of @PersistenceContext)http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
thank you
/Michael O'Brien
http://www.eclipselink.org

Proble with eclipselink 2.1.3 migration towards version 2.3.* or 2.4.*

Hello guys,
I ran into a problem last week when trying to deploy our application on Weblogic 12c. (12.1.1). Until now our application was running on weblogic 10.3.4.
Several of our JPA queries do not compile/execute anymore due to the new eclipselink version : 2.3.1 embedded in weblogic 12.1.1.
On weblogic 10.3.4 the JPA queries work fine (eclipselink version 2.1.3). On 12c, with eclipselink version 2.3.1, we get a ORA-0904 error on several queries. Eclipselink 2.3.1 does not compile the query into a correct native SQL query (same problem as http://www-01.ibm.com/support/docview.wss?uid=swg24022303).
Error : Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00904: "T5"."M_FOR_ID_LIE": invalid identifier
The JPA query :
SELECT DISTINCT cla FROM Classe cla, IN (cla.aet.formation.MVfos) mvfo
WHERE cla.ans = :ansCode
AND cla.lycee.id = :lyceeid
AND mvfo.ans = :ansCode AND cla.aet.niveauEtudes IN :nEtudes
// Is a child of me selected?
AND (EXISTS (SELECT mvfo2.id FROM MVfo mvfo2 WHERE mvfo.MFor.id = mvfo2.MFor.formationLie.id AND mvfo2.id IN :mvfoids)
// Is the parent of myself selected?
OR EXISTS(SELECT mvfo3.id FROM MVfo mvfo3 WHERE mvfo.MFor.formationLie.id = mvfo3.MFor.id AND mvfo3.id IN :mvfoids)
// Is a "brother" of myself selected (and it's not me)?
OR EXISTS(SELECT mvfo4.id FROM MVfo mvfo4 WHERE mvfo.MFor.formationLie.id = mvfo4.MFor.formationLie.id AND mvfo4.id IN :mvfoids AND mvfo.id <> mvfo4.id))
ORDER BY cla.code
The resulting SQL :
SELECT DISTINCT t0.ID, t0.ALIAS, t0.ANS, t0.CLOTURE_P1, t0.CLOTURE_P1_NOTES, t0.CLOTURE_P1_REGENT, t0.CLOTURE_P2, t0.CLOTURE_P2_NOTES, t0.CLOTURE_P2_REGENT, t0.CLOTURE_P3, t0.CLOTURE_P3_NOTES, t0.CLOTURE_P3_REGENT, t0.CODE, t0.CONSEIL_P1, t0.CONSEIL_P2, t0.CONSEIL_P3, t0.DEBUT_SAISIE_P1, t0.DEBUT_SAISIE_P2, t0.DEBUT_SAISIE_P3, t0.FIN_SAISIE_P1, t0.FIN_SAISIE_P2, t0.FIN_SAISIE_P3, t0.FORMATION_NB_HEURES, t0.FORMATION_TAUX_PRESENCE, t0.FORMATION_TITRE, t0.LECONS_P1, t0.LECONS_P2, t0.LECONS_P3, t0.MAX_ELEVES, t0.MIN_ELEVES, t0.TRI1, t0.TRI2, t0.TRI3, t0.TRI4, t0.TYPE_HORAIRE, t0.AET_ID, t0.LYC_ID, t0.ENS_ID
FROM AET t3, M_FOR t2, M_VFO t1, CLA t0
WHERE ((((((t0.ANS = ?) AND (t0.LYC_ID = ?)) AND (t1.ANS = ?)) AND (t3.NIVEAU_ETUDES IN (?,?,?,?)))
AND ((EXISTS (SELECT ? FROM M_FOR t7, M_FOR t6, M_FOR t5, M_VFO t4
                    WHERE (((t5.ID = t6.ID) AND (t4.ID IN (?))) AND (((t7.ID = t4.M_FOR_ID) AND (t5.ID = t1.M_FOR_ID)) AND (t6.ID = t7.M_FOR_ID_LIE))))
OR EXISTS (SELECT ? FROM M_FOR t10, M_FOR t9, M_VFO t8
               WHERE (((t9.ID = t10.ID) AND (t8.ID IN (?))) AND ((t9.ID = t5.M_FOR_ID_LIE) AND (t10.ID = t8.M_FOR_ID)))) )
OR EXISTS (SELECT ? FROM M_VFO t11, M_FOR t13, M_FOR t12
               WHERE ((((t9.ID = t12.ID) AND (t11.ID IN (?))) AND (t1.ID <> t11.ID)) AND ((t13.ID = t11.M_FOR_ID) AND (t12.ID = t13.M_FOR_ID_LIE)))) )) AND (((t3.ID = t0.AET_ID) AND (t2.ID = t3.M_FOR_ID)) AND (t1.M_FOR_ID = t2.ID)))
               ORDER BY t0.CODE ASC
The JPA get's confused with the scoping of the M_FOR table. We use the same table again in different subqueries. T5 is reused in the second qubquery which is wrong (it's not in the FROM). and thus we get a ORA-0904 error.
So I was hoping that I could solve this problem by upgrading to JPA version 2.4.1 which I did using the following tutorial :
http://docs.oracle.com/cd/E23943_01/doc.1111/e25034/tlandwls.htm#BABEDCEI Section 2.3.3 Task 3: Update the Version of EclipseLink in WebLogic Server.
Basically I made a shared-library with the 2.4.1 JPA and reference it from our project.
With the 2.4.1 version I run into a org.eclipse.persistence.exceptions.JPQLException on A LOT of queries even before the queries are compiled into native sql:
I have simplified a query to make it understandable :
Caused by: Exception [EclipseLink-0] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.JPQLException
Exception Description: Syntax error parsing [SELECT eleve FROM Eleve eleve WHERE CONCAT(eleve.nom, 'what is going on here') IN :modCodeList ].
The IN expression does not have a valid expression
I have the impression that the left side of a IN expression can't be a constant. If I put (eleve.nom IN :list) this query passes. If I put (1 in :list) the query fails for the same reason.
I have double checked the runtime version of eclipselink with:
logger.debug("ECLIPSELINK VERSION " + org.eclipse.persistence.Version.getVersionString());
So to summarize, I have native sql problems (incorrect sql) with versions 2.3.* and I have parsing exceptions with versions 2.4.0 and 2.4.1. I suppose that with versions 2.4.* I will run into the same native sql problems of versions 2.3.* once all the queries parse.
Versions 2.1.3 and 2.2.0 work.
Has anyone any idea or experience with migration problems of weblogic and/or eclipselink. Any help would be very appreciated.
Thanks in advance for your help.
David

EclipseLink 2.4 uses the Hermes parser by default instead of the ANTLR parser used previously, so that might explain the parsing error differences. Both issues should be filed as bugs, but it might be that once the 2.4 parse error is fixed or a workaround provided to generate the correct SQL - the code generated by the two parsers can be slightly different.
But please file both issues with as simple a test case reproduction as possible, and remember to vote for each if filed on EclipseLink instead of through Oracle support.
Best Regards,
Chris

EJB Service , 11g, Error on deployment.

I am trying to use EJB adapter in my SOA Composite.
I used Eclipselink's sdo-compiler to generate the SDO from a schema definition, and then imported them to the project.
The approach to be followed is given in this link [http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/sca_sdo_ejb.htm]
I am deploying from Jdeveloper, it compiles successfully but the deployment fails.
While deploying the composite, I get the error posted below.
where com.oracle.schemas.service.bpel.common.PropertiesTypeImpl is one of the SDO object generated by the sdo-compiler.
and from the error log it seems org.eclipse.persistence_1.0.0.0_1-1-0.jar is the library in Weblogic server to handle SDOs.
The eclipselink utility has another jar(Eclipselink.jar) that contains classes to generate SDO.
I am not sure if this is error is due to inconsistencies between the jar in Eclipselink and Weblogic server.
Any pointers to this is much appreciated.
Error log on deployment--
[11:57:26 AM] Error deploying archive sca_MessageInboundComp_rev1.0.jar to soa_server1 [lmryzd2:8001]
[11:57:26 AM] HTTP error code returned [500]
[11:57:26 AM] Error message from server:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
<HTML>
<HEAD>
<TITLE>Error 500--Internal Server Error</TITLE>
<META NAME="GENERATOR" CONTENT="WebLogic Server">
</HEAD>
<BODY bgcolor="white">
<FONT FACE=Helvetica><BR CLEAR=all>
<TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all>
<FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 500--Internal Server Error</H2>
</FONT></TD></TR>
</TABLE>
<TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New"><pre>javax.servlet.ServletException: oracle.classloader.util.AnnotatedLinkageError: Implementing class
     Invalid class: com.oracle.schemas.service.bpel.common.PropertiesTypeImpl
     Loader: default.composite.MessageInboundComp.0dcaa68c-61ab-490e-8f32-2ffa4825e13b:1.0
     Code-Source: /C:/Installed/wls11g_orahome/user_projects/domains/base_domain/deployed-composites/MessageInboundComp_rev1.0/sca_MessageInboundComp_rev1.0/0dcaa68c-61ab-490e-8f32-2ffa4825e13b/SCA-INF/lib/MessageProcessorService.jar
     Configuration: Application component in user-defined-origin
     Dependent class: org.eclipse.persistence.sdo.SDOType
     Loader: sun.misc.Launcher$AppClassLoader@20929799
     Code-Source: /C:/Installed/wls11g_orahome/modules/*org.eclipse.persistence_1.0.0.0_1-1-0.jar*
     Configuration: /C:/Installed/wls11g_orahome/modules/org.eclipse.persistence_1.0.0.0_1-1-0.jar
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:333)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.wls.JpsWlsFilter$1.run(JpsWlsFilter.java:96)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.wls.util.JpsWlsUtil.runJaasMode(JpsWlsUtil.java:146)
     at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:140)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: oracle.classloader.util.AnnotatedLinkageError: Implementing class
     Invalid class: com.oracle.schemas.service.bpel.common.PropertiesTypeImpl
     Loader: default.composite.MessageInboundComp.0dcaa68c-61ab-490e-8f32-2ffa4825e13b:1.0
     Code-Source: /C:/Installed/wls11g_orahome/user_projects/domains/base_domain/deployed-composites/MessageInboundComp_rev1.0/sca_MessageInboundComp_rev1.0/0dcaa68c-61ab-490e-8f32-2ffa4825e13b/SCA-INF/lib/MessageProcessorService.jar
     Configuration: Application component in user-defined-origin
     Dependent class: org.eclipse.persistence.sdo.SDOType
     Loader: sun.misc.Launcher$AppClassLoader@20929799
     Code-Source: /C:/Installed/wls11g_orahome/modules/org.eclipse.persistence_1.0.0.0_1-1-0.jar
     Configuration: /C:/Installed/wls11g_orahome/modules/org.eclipse.persistence_1.0.0.0_1-1-0.jar
     at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2410)
     at oracle.classloader.PolicyClassLoader.findLocalClass(PolicyClassLoader.java:1546)
     at oracle.classloader.SearchPolicy$FindLocal.getClass(SearchPolicy.java:226)
     at oracle.classloader.SearchSequence.getClass(SearchSequence.java:119)
     at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1728)
     at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1689)
     at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1674)
     at org.eclipse.persistence.sdo.helper.SDOClassLoader.loadClass(SDOClassLoader.java:70)
     at org.eclipse.persistence.sdo.SDOType.getInstanceClass(SDOType.java:151)
     at org.eclipse.persistence.sdo.SDOType.preInitialize(SDOType.java:770)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.startNewComplexType(SDOTypesGenerator.java:487)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.startComplexType(SDOTypesGenerator.java:442)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processComplexType(SDOTypesGenerator.java:397)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processGlobalComplexType(SDOTypesGenerator.java:387)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processGlobalItem(SDOTypesGenerator.java:2136)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processSimpleElement(SDOTypesGenerator.java:1292)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processElement(SDOTypesGenerator.java:1187)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processGlobalElement(SDOTypesGenerator.java:1151)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processGlobalElements(SDOTypesGenerator.java:1139)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processSchema(SDOTypesGenerator.java:244)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.define(SDOTypesGenerator.java:126)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processImportIncludeInternal(SDOTypesGenerator.java:298)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processImports(SDOTypesGenerator.java:259)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processSchema(SDOTypesGenerator.java:241)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.define(SDOTypesGenerator.java:126)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processImportIncludeInternal(SDOTypesGenerator.java:298)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processImports(SDOTypesGenerator.java:259)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processSchema(SDOTypesGenerator.java:241)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.define(SDOTypesGenerator.java:126)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processImportIncludeInternal(SDOTypesGenerator.java:298)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processImports(SDOTypesGenerator.java:259)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.processSchema(SDOTypesGenerator.java:241)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.define(SDOTypesGenerator.java:126)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.define(SDOTypesGenerator.java:117)
     at org.eclipse.persistence.sdo.helper.SDOTypesGenerator.define(SDOTypesGenerator.java:112)
     at org.eclipse.persistence.sdo.helper.delegates.SDOXSDHelperDelegate.define(SDOXSDHelperDelegate.java:299)
     at oracle.integration.platform.blocks.sdox.BaseSDOBindingComponent.registerSDOFromTypes(BaseSDOBindingComponent.java:270)
     at oracle.integration.platform.blocks.sdox.BaseSDOBindingComponent.registerSDOs(BaseSDOBindingComponent.java:208)
     at oracle.integration.platform.blocks.sdox.BaseSDOBindingComponent.registerSDOs(BaseSDOBindingComponent.java:221)
     at oracle.integration.platform.blocks.sdox.BaseSDOBindingComponent.getPortMetaData(BaseSDOBindingComponent.java:191)
     at oracle.integration.platform.blocks.sdox.BaseSDOBindingComponent.registerSDOs(BaseSDOBindingComponent.java:103)
     at oracle.integration.platform.blocks.sdox.JavaEntryBindingComponent.load(JavaEntryBindingComponent.java:386)
     at oracle.integration.platform.blocks.sdox.JavaEntryBindingComponent.load(JavaEntryBindingComponent.java:33)
     at oracle.integration.platform.blocks.deploy.DeploymentConnection.deployServices(DeploymentConnection.java:233)
     at oracle.integration.platform.blocks.deploy.DeploymentConnection.deploy(DeploymentConnection.java:90)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:161)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.loadComposite(CompositeDeploymentManagerImpl.java:84)
     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 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
     at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:70)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy214.loadComposite(Unknown Source)
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:37)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:274)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:195)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:149)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:101)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:88)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:72)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:140)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     ... 19 more
Caused by: java.lang.IncompatibleClassChangeError: Implementing class
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
     at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2364)
     ... 89 more
</pre></FONT></TD></TR>
</TABLE>

Any clues to this one?

Hibernate 3.6 Final (JPA 2.0) + WL 10.3.x :Unable to deploy sample appn

Hi,
Is anyone able to deploy a JPA 2.0 (Hibernate 3.6 Final specifically) application on WL 10.3.x?
I tried on 10.3.2 and 10.3.3 but I get following exceptions
Caused By: java.lang.NoSuchMethodError: javax.persistence.spi.PersistenceUnitInfo.getSharedCacheMode()Ljavax/persistence/SharedCacheMode;
at org.hibernate.ejb.util.LogHelper.logPersistenceUnitInfo(LogHelper.java:39)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:516)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:352)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:332)
Or (when I set to use prefer-application-packages for javax.persistence.* and org.hibernate.*, I get the following exceptions:
Caused By: weblogic.deployment.EnvironmentException: Error processing persistence unit TrivnetEJB of module TrivnetEJB.jar: Error instantiating the Persistence Provider class org.hibernate.ejb.HibernatePersistence of the PersistenceUnit TrivnetEJB: java.lang.ClassCastException: org.hibernate.ejb.HibernatePersistence cannot be cast to javax.persistence.spi.PersistenceProvider
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:344)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:332)
at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:134)
at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:336)
at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:250)
at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:69)
at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:221)
I have seen few forums that specify a workaround for this for applications that use spring.
WebLogic 10.0 + JPA 2.0 = errors
The above forum also specifies that till WL10.3.3, full JPA2.0 support is not available. So does it mean that Hibernate 3.6 based applications won't work at all on WL 10.3.x and have to wait till 10.3.4 is released? Or is there any other solution or patch available for this.
This is really a high priority issue for us.
Please suggest.

See the recent OTN post from 20110115 detailing the latest release of Oracle WebLogic Server and some retesting of the previous issues related to JSR-317 JPA 2.0 support below.
Re: Deploy Hibernate based EAR file on Weblogic 10.3.3?
The latest release of Oracle WebLogic Server has been available on OTN at the following location since 20110115.
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
This release provides support for JSR-317 JPA 2.0 container managed applications using the QWG8 patch or a manual prepending classpath change.
In 10.3.3.0 you were required to use the FilteringClassLoader via the *<wls:prefer-application-packages>* addition to your application managed persistence unit - this workaround as well as the persistence.xml renaming one is now fully deprecated and not required in 10.3.4.0 for both application and container managed persistence contexts.
As of 20110115 the 5 outstanding issues below look to be fixed by applying the http://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309 patch for QWG8 or manually prepending to the WebLogic 10.3.4.0 server classpath.
commEnv.cmd: line 67
@rem Set BEA Home
set BEA_HOME=C:\opt\wls1034r20110115
@rem Enable JPA 2.0 functionality on WebLogic Server 10.3.4 with the following patch line for commEnv.cmd:67
set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.0.0.0_2-0-0.jar;%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-0.jar
A JPA 2.0 EE application using EclipseLink as the JPA2 persistence provider on WebLogic is detailed in the analysis section below1) JPA 2.0 XSD parsing - verified
2) New JPA 2.0 schema elements like <shared-cache-mode>NONE</shared-cache-mode> - verified
3) JPA 2.0 runtime API like a entityManager.getMetamodel(); call on the Servlet or Stateless session bean - verified
4) JPA 2.0 weaving/instrumentation - this will require a more detailed lazy model and more debugging to fully verify
5) Dependency Injection of a container managed JPA 2.0 entityManager on a EJB component like a stateless session bean - verified
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
OTN downloadhttp://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
Patching
http://download.oracle.com/docs/cd/E18476_01/doc.220/e18480/weblogicchap.htm
Documentationhttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13852/toc.htm
Supported Oracle WebLogic Server Versionshttp://download.oracle.com/docs/cd/E15315_06/help/oracle.eclipse.tools.weblogic.doc/html/SupportedServerVersions.html
TopLink JPA 2.0 Specific documentation/patchinghttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309
EclipseLink Wiki: JPA 2.0 using EclipseLink on WebLogic analysis (XSD, Weaving, DI of @PersistenceContext)http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
thank you
/Michael O'Brien
http://www.eclipselink.org

Hibernate OR EclipseLink...Which is best with Weblogic and Oracle DB?

Hi All,
In my company, we are using Oracle DB and Weblogic application server. So in the process to upgrade or switch to new ORM, we shortlisted two options - Hibernate and EclipseLink.
I gathered following summary regarding both ORMs -
Hibernate:
1.     When you need to train people, like we are going to do next week – most of the companies have Hibernate experts.
2.     When you hire new developers, most of them come with specific Hibernate experience.
3.     When you need to consult with experts, both in the internet or consultants, you have LOTS of options. Endless forums and communities all regarding Hibernate.
4.     Hibernate is an open source which has a huge community. This means that it will be improved all the time and will push the ORM market forward.
5.     Hibernate is an open source which means you have the code to handle, and in case needed, fit it to your needs.
6.     There are lots of plugins to Hibernate, such as validations tool, audit tools, etc. These becomes standard as well and dismiss you from impl. things yourself.
7.     One most important thing with ORM tool, is to configure it according to your application’s needs. Usually the default setting doesn’t fit to your needs.
For that sake, when the market has a huge experience with the tool’s configuration, and lots of experts (see point 1 and 3) – most of chances you will find similar cases and
lots of knowledge about how to configure the tool and thus – your application.
EclipseLink:
1. Fully supported by Oracle. Hibernate no. In case of pb, it could be cumbersome to prove that it is a pure Weblogic one. Concretely, we will have to prove it (waste of time and complexity).
2. Eclipse link is developed by Oracle and the preferred ORM in the Weblogic /Oracle DB world.
3. Even if at a certain time EclipseLink was a bit late compared to Hibernate (feature), EclipseLink evolved very fast and we can consider now that they close the gap.
4. No additional fee as soon as you have Weblogic license. You will need to pays additional fee if you want some professional support on Hibernate.
5. We are currently relying on Hibernate for our legacy offer and are facing pb in second level cache (JGroups). Today, we are riding off this part!. Consequences are limitation in clustering approach (perf)
6. On EclipseLink side we do succeed to manage first and second level cache in a clustering approach.
7. Indeed Hibernate is open source, so you can imagine handling it. In reality, the code is so complex that it is nearly impossible to modify it. Moreover as it is LGPL, you need to feedback all the modified sources to the community systematically.
8. All tests performed by Oracle concerning Weblogic are using EclipseLink. Moreover, Oracle says that some specific optimizations are done to manage Oracle DB.
9. Hibernate comes from JBoss community.
Right now we are preferring Hibernate but there are concerns/reasons like EclipseLink developed by Oracle and preferred ORM in Webogic/ Oracle DB world (compatibility of ORM with DB and App. server), support comparison with both ORM, which are preventing to finalize the decision.
Please help me with you views and opinions and share you experience with us so that we can make a perfect decision.
If you want you can also reply to me @ [email protected].
Thanks.

The way the ORMs are designed, integration with application servers are relatively simple, and all provides the same features. Also since WebLogic have been around for a while, all ORMs are all well tested in this configuration.
Hibernate has lot more users, and is likely very often used with Oracle DB, so you can expect not much bug against Oracle DB, maybe even less bug than EclipseLink, which is not much used. EclipseLink does provide support for some esoteric Oracle DB features like hierarchical and flashback queries.
OpenJPA and DataNucleus are also JPA compliant. It’s likely that Open JPA has a higher user base than EclipseLink, so less unknown bugs.
Oracle paying support is well known to be a bad joke. It’s a negative return to use this channel, even if they would be free. So in reality, you end up to use the open (free) forum to get support.
What’s was lacking with Hibernate before is Dynamic Fetch Planning, but they now have some support, see http://opensource.atlassian.com/projects/hibernate/browse/HHH-3414. OpenJPA was the first to implement this must have.
EclipseLink has query in memory, which can be used, but the API do not help to leverage it, and EclipseLink’s leadership made it clear that they are not going to make it better, instead they want to push Coherence cache.
Hibernate has an open API for second level cache, which mean you can get out of problem by using another implementation, for example, EHCache seems to be professionally tested, so I would be surprise you find obvious bugs.
I cannot comment on Hibernate source code quality, but I can tell you that locking mechanism in EclipseLink is used to be very fragile, and many concepts are dispersed over the code base.
The runtime monitoring of Hibernate have always been great due to the fact that JBoss have always been strong on JMX, EclipseLink has not much usable features on this.
If I would be you, I would consider OpenJPA or Hibernate instead of EclipseLink, the main reason is that because EclipseLink has a so low user base, I have found lot of obvious bugs in production, like if I was the only user of it. Then, when I submitted bugs to the small development team, which do not encourage user base contribution, they were too busy trying to keep up adding the JPA interfaces on top of their existing proprietary APIs.

Weblogic Eclipselink Sequence Table Connection Pool Sequence Separate transaction while JTA on main transaction

Hi,
And thanks in advance for your support.
In weblogic 12, managing to get the eclipse link connection sequencing mechanism when one uses Tables for sequencing entity ids seems to be complicated.
QUICK REFERENCE:
http://www.eclipse.org/eclipselink/api/2.5/org/eclipse/persistence/config/PersistenceUnitProperties.html
The concept:
While having EJB, MDBs etc... run on a JEE container, be it glassfish or weblogic, it should be possible to have the main thread transaction be managed as part of JTA global transactions by the contianer.
Namely, pumping messages to JMS queues, persisting entities etc.
Meanwhile, it should be also possible to as the transaction is on going write and update entity ids from sequencing tables.
For this very purpose, eclipse link provides persistence.xml properties, such as the now deprecated eclipselink.jdbc.sequence-connection-pool" value="true", to fullfill this very purpose.
This option greatly avoids dead longs, by allowing eclipse link to fetch a non JTA managed connection, pseudo "two phase locking read table update table" go to the datbase and fetch a new sequence.
The same mechnism under JTA is a disaster. A transaction that creates ten different entities, might do ten reads and updates on this table, while mean while a competing transaction might be trying to do the same. It is guaranteed dead lock with minimal stress on the environment.
Under glassfish, for example, tagging a persistence.xml with :
<persistence-unit name="MY_PU" transaction-type="JTA">
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <jta-data-source>jdbc/DERBY_DS</jta-data-source>
        <non-jta-data-source>jdbc/DERBY_DS</non-jta-data-source>
        <properties>
            <property name="eclipselink.jdbc.sequence-connection-pool" value="true" />
        </properties>
</peristence-unit>
does miracles, when entities are using TABLE sequencing.
Under weblogic, say you are using the Derby embedded XA driver with two phase commit, deploying the applicaiton immediately leads to:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Cannot call commit when using distributed transactions
Error Code: 0
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicCommitTransaction(DatabaseAccessor.java:426)
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.commitTransaction(DatasourceAccessor.java:389)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:409)
at org.eclipse.persistence.internal.sequencing.SequencingManager$Preallocation_Transaction_Accessor_State.getNextValue(SequencingManager.java:579)
at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067)
at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70)
at org.eclipse.persi
While weblogic is right that their might be a distributed transaction ongoing, it is mistaken in the fact tha tthe connection requested by eclipse link for generating the ID should be part of the global transaciton.
Eclipse link provides other ways to attempt to configure the sequencing mechanism, by sating for example a non-jta transaction.
I have attempted also using these properties both withe original data DERBY_DS that uses the XA driver, and later with a new data source i created on purpose to try to work around the sequencing contengy.
For example:

            
This new DERBY_SEQUENCING_NON_JTA is explicitly configured to use a NON_XA driver with global transactions flag set to disabled.
Regardless, the only thing I get out of this is that the application is deployed and super fast, up to the point where i stress it with a system test that introduces some degreee of concurrency, and then I see the dead locks on the sequencing table.
Meaning that the ongoing transactions are holding tight to their locks on the sequencing table.
Is this a known issue?
Is there something I am missing in the configuration?
It really should not be this diffcult to get eclipse link to run its sequence reads and updates on a separate transaction of the main JTA transaction, but so far looks impossible.
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
Error Code: 30000
Call: UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?
bind => [2 parameters bound]
Query: DataModifyQuery(name="MyEntity_Gen" sql="UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?")
Many thanks for your help.

Are you calling the cmp bean code and your new Sql code under a same transactional context?
The following setting
"rollbackLocalTxUponConnClose=true"
will make the connectionpool to call the rollback method on the connection object before keeping it back in the pool. In your sql code if you are calling connection.close() , then your entire transaction will be rolled back.
CMP bean requires a transactional connection while communicating with the database.
What is the sequence of code execution?
I think you must be calling sql code first and then cmp bean code later.
You may avoid this problem in this way. This is my guess based on my understanding on your code execution.
1. set rollbackLocalTxUponConnClose=false
Execute the sql code and cmp code in a single transaction (in a single session bean method with cmt or bmt transaction ). Specify tx.rollback if it is bmt. or call tx.setRollbackOnly() if it is a cmt. In this way you will have control to roll back the transactions.
Hope this helps you.
bmt-> bean managed transaction
cmt-> container managed transaction.
Regards,
Seshi.

Eclipselink issue on weblogic 10.3

We have two different application using eclipselink file bundled as part of application. Application works fine if either of application deployed on server. If we deploy both application on server, the application which first accessed works fine other application gives error "Predeployement of PersistenceUnit failed".
Environment
WebLogic 10.3
JRE 1.6
Application structure-
App.ear
- META-INF
- application.xml
- MANIFEST.MF
- weblogic-application.xml
- APP-INF
- lib
- eclipselink.jar
- dependency-n.jar
- app.war

We have two different application using eclipselink file bundled as part of application. Application works fine if either of application deployed on server. If we deploy both application on server, the application which first accessed works fine other application gives error "Predeployement of PersistenceUnit failed".
Environment
WebLogic 10.3
JRE 1.6
Application structure-
App.ear
- META-INF
- application.xml
- MANIFEST.MF
- weblogic-application.xml
- APP-INF
- lib
- eclipselink.jar
- dependency-n.jar
- app.war

Upgrade EclipseLink in Embedded WebLogic Server (JDeveloper 11.1.1.2.0)

Currently I am using JDeveloper 11.1.1.2.0 for my project, which comes with EclipseLink v1.2 pre-installed. However, my project requires to use latest EclipseLink version 2.0. I added EclipseLink 2.0 into Libraries and Classpath setting in project property. However, when I ran my app by using embedded WebLogic Server, my app is still using the old EclipseLink v1.2. I already tried to copy EclipseLink 2.0 jar file into DefaultDomain/lib directory and ear library directory. But embedded weblogic server still using old version from modules directory. Could anyone tell me how I could solve this issue. Thanks!

WebLogic comes pre-configured with TopLink's provided EclipseLink Library as a system module. You cannot upgrade this to 2.0 in a support fashion. The next release of WebLogic will include EclipseLink 2.0(.x).
If you want to test your application's use of EclipseLink 2.0 using JPA 1.0 application managed EntityManagers you can package the 2.0 library in your EAR and use the filtered classloader config setup in the weblogic-application.xml to ensure the packaged library is used instead of the system module.
Doug

Error while deploying a war file in Oracle Weblogic 10gr3 server

Hi
I am trying to deploy a web application which uses Hibernate 3 in Oracle weblogic 10gr3.But I am getting following exception.The same application gets deployed in tomcat without any problem.
urce [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'autoMeteringInterceptor' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'validator' while setting bean property 'validator'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'tenant.tenantService' while setting bean property 'tenantService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenant.tenantService' defined in ServletContext resource [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId
     at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:256)
     at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
     at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
     at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:273)
     at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
     at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
     at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
     at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
     at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'tenant.tenantService' while setting bean property 'tenantService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenant.tenantService' defined in ServletContext resource [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId
     at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:256)
     at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
     at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
     at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
     at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:248)
     at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
     at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
     at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:273)
     at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
     at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
     at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
     at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
     at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Initially this application was giving me absolute path related errors.But when I made changes to applicationContext.xml as follows,giviing absolute path for Hibernate mapping files
<property name="mappingDirectoryLocations">
     <list>
     *<value>file:D:\saas-mappings</value>*
     </list>
</property>
I have extrached all the *.hbm.xml file to above location that is D:\saas-mappings.But now the application is giving me above mentioned error.The error says that it is related to Named queries.I am pasting the contents of a sample *.hbm.xml file having named query as a sample
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="com.psl.saas.domain">
     <class name="TenantSlaUsage" table="tenantslausage_v2">
               <id name="tenantId" column="tenantId">
               </id>
               <property name="maxValue">
                    <column name="maxValue"></column>
               </property>
               <property name="thresholdValue">
                    <column name="thresholdValue"></column>
               </property>
               <property name="slaType" column="slaType" type="com.psl.saas.dataservice.SaasEnumSlaType"/>
               <many-to-one name="slaCriterion" class="SLACriterion" column="slaCriterionName" lazy="false" unique="true" />
               <property name="usageCount">
               <column name="usageCount"></column>
               </property>
     </class>
     *<query name="slaUsageOfTenant.bySlaCriterion">
          <![CDATA[from com.psl.saas.domain.TenantSlaUsage where tenantId=:tenantId and slaCriterionName=:slaCriterionName]]>
     </query>*
</hibernate-mapping>
Any help on this will be greatly appreciated
Thanks in Advance
-Sameer Gijare

Hi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org

Error starting managed server weblogic 10.3.5

hi my jdeveloper is 11.1.2.0 and my weblogic is 10.3.5 am having error when trying to start my managed server
the error am geting is
or
        at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(X
AConnectionEnvFactory.java:494)
        at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(X
AConnectionEnvFactory.java:177)
        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourceP
oolImpl.java:1249)
        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourceP
oolImpl.java:1166)
        at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.
java:249)
        Truncated. see log file for complete stacktrace
>
<24 Jan 2014 11:03:14 AM> <Warning> <JDBC> <BEA-001129> <Received exception whil
e creating connection for pool "jdbc/HRDS": Listener refused the connection with
the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descript
or
>
<24 Jan 2014 11:03:15 AM> <Error> <Deployer> <BEA-149205> <Failed to initialize
the application 'jdbc/HRDS' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
        at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:302)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:517)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:52)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:159)
        Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: Listener refused the connection wi
th the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descript
or
        at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(X
AConnectionEnvFactory.java:494)
        at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(X
AConnectionEnvFactory.java:177)
        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourceP
oolImpl.java:1249)
        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourceP
oolImpl.java:1166)
        at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.
java:249)
        Truncated. see log file for complete stacktrace
>
<24 Jan 2014 11:03:17 AM> <Error> <Deployer> <BEA-149205> <Failed to initialize
the application 'wsm-pm' due to error weblogic.management.DeploymentException: [
J2EE:160149]Error while processing library references. Unresolved application li
brary references, defined in weblogic-application.xml: [Extension-Name: oracle.w
sm.seedpolicies, Specification-Version: 11.1.1, Implementation-Version: 11.1.1,
exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing lib
rary references. Unresolved application library references, defined in weblogic-
application.xml: [Extension-Name: oracle.wsm.seedpolicies, Specification-Version
: 11.1.1, Implementation-Version: 11.1.1, exact-match: false].
        at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(
CheckLibraryReferenceFlow.java:26)
        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:613)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:52)
        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:184)
        at weblogic.application.internal.EarDeployment.prepare(EarDeployment.jav
a:58)
        Truncated. see log file for complete stacktrace
>
<24 Jan 2014 11:03:18 AM> <Notice> <SipServer.Resource> <BEA-332401> <Initializi
ng SipServer Resource with configuration com.bea.wcp.sip.management.descriptor.b
eans.SipServerBeanImpl>
<24 Jan 2014 11:03:18 AM> <Notice> <WLSS.Engine> <BEA-330071> <WebLogic Sip Serv
er "madimad-b533821" patch version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:3
3 PST 2010 1384255
Javax Server Pages Client Capable 1.2 Tue Jul 13 02:43:41 EDT 2010
Expression Language 2.1 for JSP 1.0 Sun Jul 18 23:17:34 PDT 2010
Javax Enterprise Servlets Client Capable 1.0 Thu Aug 2 12:41:25 EDT 2007
Eclipse Java Development Tools 3.5.2 Thu Sep 2 09:47:11 EDT 2010
WebLogic java compiler utils package Client Capable 1.2 Thu Feb 11 03:38:50 EST
2010
WebLogic WebApp Container Public API Client Capable 1.4 Fri Oct 1 20:01:15 PDT 2
010
Oracle WebLogic Server Module Dependencies 10.3 Thu Oct 28 06:03:12 PDT 2010
ANTLR Java based compiler generator Client 2.7 Mon Jun 11 12:19:48 EDT 2007
WebLogic Descriptors for J2EE 1.5 Wed May 5 14:32:58 EDT 2010
WebLogic Descriptors for J2EE 1.5 Binding Bundle
WebLogic Specific Descriptors 1.3 Tue Sep 14 18:48:42 PDT 2010
WebLogic Specific Descriptors 1.3 Binding Bundle
WebLogic Datasource 1.9 Tue Oct 26 13:50:26 PDT 2010
WebLogic Datasource 1.9 Binding Bundle
WebLogic Beangen Client Capable 1.7 Wed Feb 24 16:02:48 PST 2010
WebLogic Beangen 1.7 Binding Bundle
WLDF Accessor Client Capable 1.5 Fri Sep 3 17:10:52 EDT 2010
WLDF Accessor 1.5 Binding Bundle
WebLogic Management Core Interfaces Client Capable 2.8 Wed Aug 11 08:20:03 PDT 2
010
WebLogic Management Core Interfaces 2.8 Binding Bundle
WebLogic EJBGen Client Capable 1.1 Thu Jun 3 13:17:07 EDT 2010
Apache Byte Code Engineering Library (BCEL) extracted from 5.2.zip from http://j
akarta.apache.org/site/downloads/downloads_bcel.cgi with packages renamed from o
rg.apache.bcel to com.bea.core.repackaged.apache.bcel Client 5.2 Tue May 15 09:5
2:37 EDT 2007
Apache commons collections package 3.2 Tue Mar 20 15:48:25 MDT 2007
Apache commons lang package 2.1 Tue Mar 20 15:48:30 MDT 2007
Apache commons pool package 1.3 Tue Mar 20 15:48:36 MDT 2007
Apache commons io 1.4 package 1.0 Wed Jun 2 17:36:36 EDT 2010
Apache commons fileupload 1.2.1 package 1.0 Wed Jun 2 17:36:36 EDT 2010
Apache DOM implementation 1.0 Tue Mar 20 15:36:46 MDT 2007
Apache Logging Support 1.0 Tue Mar 20 15:36:50 MDT 2007
Apache OpenJPA classes 1.2 Thu Jul 22 05:16:07 EDT 2010
XMLBeans - Apache SVN rev 962560 2.1 Thu Jul 15 09:52:54 EDT 2010
BEA Logging Runtime Support Client Capable 1.8 Mon Jun 7 12:07:02 PDT 2010
BEA Common Security Open SAML 1.0 Fri May 14 20:18:10 PDT 2010
BEA OpenSAML 2.0 1.0 Wed Mar 24 13:18:27 PDT 2010
bea-harvester-api2.0 Client Capable 2.3 Mon Feb 15 14:41:06 EST 2010
bea-harvester-jmx2.0 Client Capable 2.3 Wed Feb 3 11:54:03 PST 2010
bea-harvester-utils Client Capable 1.4 Mon Feb 15 14:41:06 EST 2010
bea-mbean-typing-util 1.4 Wed Feb 24 19:15:33 EST 2010
Javolution 3.7.19 3.7 Tue Aug 28 17:32:21 PDT 2007
Joda-time 1.2.1 1.2 Tue Aug 28 17:32:27 PDT 2007
BEA STAX Build Time Support 1.5 Tue May 4 07:32:25 PDT 2010
BEA STAX Runtime Time Support Client Capable 1.7 Wed Aug 4 19:40:47 EDT 2010
BEA Generic Annotations Client Capable 1.3 Sat Jul 11 00:30:54 EDT 2009
BEA Kodo 1.3 Tue Dec 7 12:34:59 PST 2010
BEA Kodo Integration Client Capable 1.6 Sun Nov 22 16:29:06 PST 2009
BEA Kodo Integration 1.6 Binding Bundle
BEA Kodo Integration Tools 1.3 Sat Feb 13 09:30:33 PST 2010
XML Beans Marshalling (package renamed com.bea) SVN 962560 2.2 Thu Jul 15 09:52:
54 EDT 2010
WebLogic Utils Client Capable 1.9 Thu Nov 11 13:50:07 PST 2010
Aspect 5.3 Fri Jun 4 14:55:18 PDT 2010
BEA Apache Commons Logging Repackaged 1.2 Mon Jun 11 12:47:12 EDT 2007
Spring Framework 1.1 Thu Dec 3 12:21:08 EST 2009
Pitchfork 1.3 Thu Jun 3 13:17:07 EDT 2010
${description} 1.2 Fri Jun 25 16:25:26 EDT 2010
CSS i18n 1.0 Fri Oct 8 10:32:52 EDT 2010
CSS xacml 1.0 Fri Oct 8 10:32:52 EDT 2010
SAML2 Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Engine Implementation 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Engine Interfaces 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security API 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Implementation 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security JDK Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
Common Security SAML 2.0 1.0 Fri Oct 8 10:32:52 EDT 2010
Common Security SAML 2.0 Management JavaBeans 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Provider Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
SAML Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
XACML Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Provider Environment 1.0 Fri Oct 8 10:32:52 EDT 2010
RSA certj 3.1 Wed May 5 15:11:55 PDT 2010
Netscape LDAP JDK 1.2 Mon Jun 7 15:56:47 EDT 2010
Commons Networking Utilty classes 1.0 Wed Feb 6 15:01:03 PST 2008
WebLogic SAAJ 1.6 Wed Jun 16 22:02:31 EDT 2010
WebLogic STAX Client Capable 1.8 Sat May 15 16:38:03 EDT 2010
jaxb-impl.jar taken from Glassfish JAXB 2.1.9 1.0 Fri Aug 20 14:37:07 EDT 2010
jaxb-impl.jar taken from Glassfish JAXB 2.1.12 1.0 Thu May 6 16:10:04 PDT 2010
resolver.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu Dec 3 11:46:24 EST 2009
Fastinfoset.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu Dec 3 11:46:27 EST 2009
jaxws-rt.jar taken from Glassfish JAXWS 2.1.5 1.1 Wed Oct 13 20:37:41 PDT 2010
Java.net implementation of MimePull.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu
Dec 3 11:46:33 EST 2009
Codehaus STaX Interfaces 3.0.1 1.0 Mon Mar 8 20:49:50 PST 2010
Woodstox STaX Parser 4.0.5 1.0 Thu Dec 3 11:35:43 EST 2009
jaxws-tools.jar taken from Glassfish JAXWS 2.1.5 1.1 Fri Sep 24 17:55:05 PDT 201
0
Java.net Stax Extensions 1.0 Tue Jun 3 07:12:06 PDT 2008
Java.net xml stream buffer 1.0 Tue Mar 17 05:24:12 PDT 2009
Jakarta ORO 1.0 Wed Feb 6 15:01:03 PST 2008
Javax Enterprise Activation 1.1 Tue Apr 8 09:31:17 PDT 2008
Javax Annotation 1.0 Fri Dec 25 09:02:47 PST 2009
Javax Interceptor 1.0 Tue Mar 20 15:37:16 MDT 2007
Javax Enterprise Beans 3.0 Mon Jun 11 12:21:01 EDT 2007
Java Data Objects 2.0 Mon Jun 11 12:20:56 EDT 2007
Java Enterprise Deployment APIs 1.2 Tue Mar 20 15:37:28 MDT 2007
Java Enterprise Messaging 1.1 Mon Jun 11 12:21:11 EDT 2007
Java Web Services 2.0 Tue Mar 20 15:37:37 MDT 2007
Javax Enterprise Mail 1.1 Mon Jul 6 10:41:09 MDT 2009
Java Enterprise Management APIs 1.0 Tue Mar 20 15:37:49 MDT 2007
Java Persistence Client Capable 1.0 Tue Oct 7 12:18:34 PDT 2008
Java Connector 1.5 Mon Jun 11 12:22:07 EDT 2007
Java Authorization Contract for Containers 1.0 Wed Feb 6 15:01:03 PST 2008
Javax Transaction APIs Client Capable 1.0 Thu Aug 2 12:42:14 EDT 2007
JAXB 2.1 Mon Jun 11 12:22:53 EDT 2007
Java XML Registry 1.0 Wed Feb 6 15:01:03 PST 2008
Java XML Soap Extensions 1.3 Mon Jun 11 12:22:59 EDT 2007
Java Stream XML Extensions 1.1 Mon Jun 11 12:23:05 EDT 2007
JAX-WS APIs 2.1 Mon Jun 11 12:23:16 EDT 2007
Java API for XML-based RPC   1.2 Mon Jun 11 12:23:10 EDT 2007
Monfox Dynamic SNMP Agent 1.1 Fri Mar 19 05:46:27 MDT 2010
Serp bytecode manipulation framework 1.14.3 Fri Jun 11 12:06:08 PDT 2010
WebLogic Apache Classes Client Capable 1.2 Thu Feb 18 22:06:19 PST 2010
WebLogic BeanInfo Caching and Discovery Client Capable 2.4 Sat Oct 25 20:46:29 P
DT 2008
WebLogic Descriptor Client Capable 1.9 Tue Jul 20 16:03:09 EDT 2010
Repackaged ASM-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-commons-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-tree-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-util-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Oracle JFR 1.0 Thu Feb 18 19:06:33 PST 2010
WebLogic Diagnostics Core Interfaces Client Capable 2.5 Thu Jun 3 05:20:41 PDT 2
010
WebLogic Diagnostics Logging Client Capable 1.2 Fri Dec 12 11:37:59 MST 2008
WebLogic Diagnostics Query Module Client Capable 1.2 Tue Oct 27 02:48:36 PDT 200
9
WebLogic Diagnostics Instrumentor Tool 1.7 Tue May 18 03:51:46 PDT 2010
WebLogic Diagnostics Instrumentor Config Tool 1.7 Tue Jun 29 16:41:19 EDT 2010
WebLogic Diagnostics JRockit Flight Recorder Interfaces Client Capable 1.1 Fri O
ct 29 16:32:05 EDT 2010
Diagnostics Notifications Module Client Capable 1.4 Sun Nov 22 16:03:32 PST 2009
BEA Logging Runtime Support Client Capable 1.5 Thu Apr 29 20:43:42 EDT 2010
WebLogic i18n Runtime Support Client Capable 1.8 Fri Sep 10 08:12:34 EDT 2010
WebLogic i18n Build Support Client Capable 1.5 Fri Feb 19 15:03:15 EST 2010
WebLogic I18N tools Client Capable 1.3 Sun Nov 22 16:03:32 PST 2009
WebLogic Management JMX Interfaces 1.4 Thu Aug 12 11:16:22 PDT 2010
WebLogic Security Provider Generation Tool 1.5 Wed Oct 14 16:39:28 MDT 2009
WebLogic Security Provider Generation Tool Client Capable 1.5 Wed Oct 14 16:39:2
8 MDT 2009
WebLogic Messaging Kernel Client Capable 1.8 Mon Aug 23 21:42:11 EDT 2010
WebLogic Resource Pool Client Capable 1.7 Mon Sep 27 12:00:08 EDT 2010
WebLogic Socket Muxer API Client Capable 1.2 Thu Apr 1 21:16:27 EDT 2010
WebLogic RMI Client Capable 1.8 Fri Sep 24 18:35:21 EDT 2010
Common Security WebLogic Server Integration Support 1.0 Fri Oct 8 10:32:52 EDT
2010
Server Lifecycle Interfaces Client Capable 1.4 Fri Feb 19 15:03:15 EST 2010
WebLogic Store Client Capable 1.7 Fri Dec 17 16:52:31 EST 2010
WebLogic STORE GXA Client Capable 1.6 Mon Aug 23 21:16:10 EDT 2010
WebLogic Store Admin Tool Client Capable 1.2 Thu Jan 21 10:24:18 PST 2010
WebLogic JDBC Store Client Capable 1.3 Mon May 17 10:46:33 PDT 2010
WebLogic JTA implementation Client Capable 2.7 Fri Sep 17 12:19:45 PDT 2010
WebLogic Utils 1.9 Thu Nov 11 13:50:07 PST 2010
Agent Utililities 1.1 Tue Feb 16 00:16:03 EST 2010
WebLogic Utility Classloader implementations Client Capable 1.8 Mon Jun 28 19:28
:16 PDT 2010
WebLogic Utils for working with Expressions Client Capable 1.4 Tue Sep 29 14:45:
53 EDT 2009
WebLogic Utils for Dynamically Generated Class Wrappers Client Capable 1.4 Fri F
eb 13 14:44:23 MST 2009
WebLogic Timers Client Capable 1.7 Thu Feb 18 13:08:44 EST 2010
WebLogic Work Manager Client Capable 1.9 Mon Oct 11 18:25:35 EDT 2010
WebLogic Workarea Client Capable 1.7 Wed Feb 24 17:18:56 PST 2010
WebLogic XML XPath Implementation Client Capable 1.4 Mon Feb 22 15:07:14 PST 201
0
Weblogic Tuxedo Connector Core Client Capable 1.5 Sat Jul 3 19:05:38 EDT 2010
WebLogic Security 1.0 Fri Oct 8 10:32:52 EDT 2010
Weblogic Server Java Authentication Helper Classes Client Capable 1.1 Mon Jul 5
20:42:35 EDT 2010
Weblogic Server Message Digest Utilities Client Capable 1.0 Thu Aug 2 12:51:30 E
DT 2007
Weblogic Server Authenticated Subject Client Capable 1.1 Thu Oct 28 05:46:37 PDT
2010
Weblogic Server Authenticated Subject Client Capable 1.5 Thu Sep 9 10:23:21 MDT
2010
PrintingSecurityManager - PSM 1.1 Tue Feb 16 05:30:08 PST 2010
WebLogic security ssl classes 1.0 Tue Jun 15 17:39:53 EDT 2010
WebLogic Nodemanager Plugin Client Capable 1.3 Tue Nov 18 18:23:10 EST 2008
nodemanager module for managed processes 1.0 Thu Apr 8 15:14:38 PDT 2010
WebLogic JMS Pool Client Capable 1.7 Mon Sep 27 12:00:08 EDT 2010
Contains compiled schema type from WLS 9.0 for WLP compatibility 1.3 Wed Feb 24
19:15:33 EST 2010
WebLogic Http Pub/Sub Module Client Capable 1.6 Mon Jul 12 02:31:07 EDT 2010
Class Redefinition Project 1.5 Mon May 10 19:48:21 EDT 2010
Class Redefinition Project Client Capable 1.5 Mon Apr 5 17:00:52 PDT 2010
Class Redefinition Project 1.5 Binding Bundle
Commonj SDO 1.0 Wed Sep 24 19:11:23 PDT 2008
WebLogic Coherence Descriptor 1.1 Wed May 5 15:17:47 EDT 2010
WebLogic Coherence Descriptor 1.1 Binding Bundle
This module contains all message catalogs 1.1 Fri Dec 17 08:04:35 PST 2010
WebLogic WebService Public API's 1.1 Tue Sep 21 22:15:05 EDT 2010
WebLogic EclipseLink Integration 1.0 Thu Feb 25 14:56:43 PST 2010
WebLogic SCA Client 1.0 Thu Feb 25 00:27:10 EST 2010
WebLogic RAC Module UCP Client Capable 1.0 Mon Sep 13 09:03:00 PDT 2010
Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu S
ep 23 15:02:15 PDT 2010
BEA Patches of apache ant Client Capable 1.2 Wed Jan 13 08:48:17 PST 2010
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server Datatier 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
WebLogic SIPServer Extension API 10.3.4.0 at 709997 built on 2010/09/27
WebLogic SIPServer Extension API 10.3.4 at 709997 built on 2010/09/27
WebLogic SIPServer CallState 10.3.4 at 709997 built on 2010/09/27
Oracle WebLogic Communications SCTP 10.3.1 at 688160 built on 2009/03/11
WebLogic WebService Databinding Plugins 1.2 Fri Oct 15 07:38:46 PDT 2010
WebLogic WebService Databinding 1.2 Fri Oct 15 06:35:13 PDT 2010
WebLogic SIP Activator 10.3.4 at 710163 built on 2010/09/30
>
<24 Jan 2014 11:03:25 AM> <Error> <WLSS.Engine> <BEA-330075> <There are no sip n
or diameter channels targeted to server "madimad-b533821">
<24 Jan 2014 11:03:25 AM> <Error> <WLSS.Engine> <BEA-330049> <Failed to start th
e sip service, shutting down>
C:\mydomain\base_domain\bin>

i did but there is no respond
i started the database
C:\mydomain\base_domain\bin>startManagedWebLogic.cmd madimad-b533821
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=
128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C
:\PROGRA~1\Java\JDK16~1.0_2\lib\tools.jar;C:\mywls\wlserver\server\lib\weblogic_
sp.jar;C:\mywls\wlserver\server\lib\weblogic.jar;C:\mywls\modules\features\weblo
gic.server.modules_10.3.4.0.jar;C:\mywls\wlserver\server\lib\webservices.jar;C:\
mywls\modules\ORGAPA~1.1/lib/ant-all.jar;C:\mywls\modules\NETSFA~1.0_1/lib/ant-c
ontrib.jar;C:\oracle\Middleware\wlserver_10.3\sip\server\lib\weblogic_sip.jar;C:
\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\mywls\wlserver\co
mmon\derby\lib\derbyclient.jar;C:\mywls\wlserver\server\lib\xqrl.jar
PATH=;C:\mywls\wlserver\server\native\win\32;C:\mywls\wlserver\server\bin;C:\myw
ls\modules\ORGAPA~1.1\bin;C:\PROGRA~1\Java\JDK16~1.0_2\jre\bin;C:\PROGRA~1\Java\
JDK16~1.0_2\bin;C:\Program Files\PC Connectivity Solution\;C:\product\11.2.0\dbh
ome_1\bin;C:\product\11.2.0\dbhome_1;C:\forms;C:\DevSuiteHome_1\jlib;C:\Program
Files\PHP;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Fil
es\Common Files\Roxio Shared\DLLShared;C:\Program Files\Common Files\Roxio Share
d\DLLShared;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared;C:\Program
Files\Common Files\DivX Shared;c:\Program Files\Java\jdk1.6.0_21\bin;C:\Program
Files\Common Files\Roxio Shared\10.0\DLLShared;C:\Program Files\Common Files\Rox
io Shared\DLLShared;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared;C:
\mywls;C:\mydomain\base_domain\bin;C:\Program Files\Java\jre6\bin\client;C:\Prog
ram Files\Java\jre6\bin;C:\Program Files\Java\jdk1.6.0_21\jre\bin;C:\Program Fil
es\Java\jdk1.6.0_21\bin;C:\Program Files\Java\jdk1.6.0_21;C:\Program Files\Java\
jre6;C:\DevSuiteHome_1\forms;C:\DevSuiteHome_1\cgenf61\admin;C:\DevSuiteHome_1\f
orms;C:\forms\sms_code.pll;C:\mywls\wlserver;C:\Java\jdk1.6.0_21;C:\mywls\wlserv
er\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and   *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console        *
starting weblogic with Java version:
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client   -Xms256m -Xmx512m -XX:CompileThr
eshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=madimad-b533
821 -Djava.security.policy=C:\mywls\wlserver\server\lib\weblogic.policy -Dweblog
ic.security.SSL.trustedCAKeyStore="C:\mywls\wlserver\server\lib\cacerts" -Xveri
fy:none -ea:com.bea.wcp...   -da -Dplatform.home=C:\mywls\wlserver -Dwls.home=C:
\mywls\wlserver\server -Dweblogic.home=C:\mywls\wlserver\server -Dcommon.compon
ents.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.
logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\mydomai
n\BASE_D~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1
.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\mydomain\BASE_D~1\config\FM
WCON~1\servers\madimad-b533821 -Doracle.domain.config.dir=C:\mydomain\BASE_D~1\c
onfig\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\mydomain\BASE_D~1\config\FMWCON~1\
carml -Digf.arisidstack.home=C:\mydomain\BASE_D~1\config\FMWCON~1\arisidprovide
r -Doracle.security.jps.config=C:\mydomain\BASE_D~1\config\fmwconfig\jps-config.
xml -Doracle.deployed.app.dir=C:\mydomain\BASE_D~1\servers\madimad-b533821\tmp\_
WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracl
e\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\mo
dules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.prot
ocol -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false
-Dweblogic.management.server=http://madimad-b533821:7001 -Dwlw.iterativeDev=fal
se -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false weblogic.Server
<24 Jan 2014 12:52:41 PM> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE
Provider self-integrity check for better startup performance. To enable this che
ck, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<24 Jan 2014 12:52:42 PM> <Info> <Security> <BEA-090906> <Changing the default R
andom Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable thi
s change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<24 Jan 2014 12:52:42 PM> <Notice> <WebLogicServer> <BEA-000395> <Following exte
nsions directory contents added to the end of the classpath:
C:\mydomain\base_domain\lib\sipactivator.jar>
<24 Jan 2014 12:52:42 PM> <Info> <Server> <BEA-002647> <The service plugin, com.
oracle.core.sip.activator, was added from C:\mydomain\base_domain\lib\sipactivat
or.jar.>
<24 Jan 2014 12:52:42 PM> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogi
c Server with Java HotSpot(TM) Client VM Version 17.0-b17 from Sun Microsystems
Inc.>
<24 Jan 2014 12:52:45 PM> <Info> <Security> <BEA-090065> <Getting boot identity
from user.>
Enter username to boot WebLogic server:tshifhiwa
Enter password to boot WebLogic server:
<24 Jan 2014 12:52:57 PM> <Info> <Management> <BEA-141107> <Version: WebLogic Se
rver 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<24 Jan 2014 12:53:01 PM> <Error> <Management> <BEA-141252> <The domain version,
10.3.5.0, is greater than the release version, 10.3.4.0, of this server.>
<24 Jan 2014 12:53:01 PM> <Error> <Configuration Management> <BEA-150001> <An er
ror occurred while connecting to the admin server to bootstrap through URL: http
://madimad-b533821:7001/bea_wls_management_internal2/Bootstrap, user: tshifhiwa
weblogic.management.configuration.ConfigurationException: [Management:141252]The
domain version, 10.3.5.0, is greater than the release version, 10.3.4.0, of thi
s server.
        at weblogic.management.provider.internal.BootStrapHelper.getBootStrapStr
uct(BootStrapHelper.java:147)
        at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(Ru
ntimeAccessImpl.java:432)
        at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
imeAccessService.java:49)
        at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
ager.java:461)
        at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
icesManager.java:166)
        at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
        at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
        at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
        at weblogic.Server.main(Server.java:71)
>
<24 Jan 2014 12:53:01 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to STARTING>
<24 Jan 2014 12:53:01 PM> <Info> <WorkManager> <BEA-002900> <Initializing self-t
uning thread pool>
<24 Jan 2014 12:53:02 PM> <Notice> <LoggingService> <BEA-320400> <The log file C
:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-b533821.log will be
rotated. Reopen the log file if tailing has stopped. This can happen on some pla
tforms like Windows.>
<24 Jan 2014 12:53:02 PM> <Notice> <LoggingService> <BEA-320401> <The log file h
as been rotated to C:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-
b533821.log00007. Log messages will continue to be logged in C:\mydomain\base_do
main\servers\madimad-b533821\logs\madimad-b533821.log.>
<24 Jan 2014 12:53:02 PM> <Notice> <Log Management> <BEA-170019> <The server log
file C:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-b533821.log i
s opened. All server side log events will be written to this file.>
<24 Jan 2014 12:54:25 PM> <Critical> <WebLogicServer> <BEA-000386> <Server subsy
stem failed. Reason: java.lang.AssertionError: Assertion violated
java.lang.AssertionError: Assertion violated
        at weblogic.utils.Debug.assertion(Debug.java:57)
        at weblogic.server.channels.ChannelService.getServerChannel(ChannelServi
ce.java:2060)
        at weblogic.server.channels.ChannelService.getServerChannel(ChannelServi
ce.java:1998)
        at weblogic.protocol.ServerChannelManager.findServerChannel(ServerChanne
lManager.java:76)
        at weblogic.ldap.EmbeddedLDAP.findLdapURL(EmbeddedLDAP.java:1482)
        Truncated. see log file for complete stacktrace
>
<24 Jan 2014 12:54:26 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to FAILED>
<24 Jan 2014 12:54:26 PM> <Error> <WebLogicServer> <BEA-000383> <A critical serv
ice failed. The server will shut itself down>
<24 Jan 2014 12:54:26 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to FORCE_SHUTTING_DOWN>

EclipseLink on WebLogic

Similar Messages

Maybe you are looking for