Community
Participate
Working Groups
Build Identifier: Eclipselink 2.2.0 I' am trying to migrate from Toplink 10.1.3 to EclipseLink 2.2.0 on Weblogic 10.3. Trying to setup cache coordination using our Tibco queues. Do not want to enable JMX or profiling. I have overriden the JMSTopicRemoteConnection and JMSTopicTransportManager to connect to the Queues with a user name and password. I'am using the following sessions.xml(not using JPA). Eclipselink send the messages over to the Topic but throws the following error when it tries to merge the changes. Any pointers would be helpful. Exception in thread "Thread-364045" java.lang.NoClassDefFoundError: org/eclipse/persistence/internal/sessions/coordination/ProfileMessageReceiveCommand at org.eclipse.persistence.sessions.coordination.RemoteCommandManager.processCommandFromRemoteConnection(RemoteCommandManager.java:236) at org.eclipse.persistence.internal.sessions.coordination.broadcast.BroadcastRemoteConnection.processReceivedObject(BroadcastRemoteConnection.java:175) at org.eclipse.persistence.internal.sessions.coordination.jms.JMSTopicRemoteConnection.onMessage(JMSTopicRemoteConnection.java:228) at org.eclipse.persistence.internal.sessions.coordination.jms.JMSTopicRemoteConnection$JMSOnMessageHelper.run(JMSTopicRemoteConnection.java:491) <?xml version="1.0" encoding="UTF-8"?> <!-- This file contains Eclipselink session configurations for the PST development environment. --> <sessions version="2.2" "links removed due to forum restriction"> <session xsi:type="server-session"> <name>default</name> <server-platform xsi:type="custom-platform"> <enable-runtime-services>false</enable-runtime-services> <enable-jta>false</enable-jta> </server-platform> <remote-command> <commands> <cache-sync>true</cache-sync> </commands> <transport xsi:type="jms-topic-transport"> <topic-host-url>tcp://tibjms:8293</topic-host-url> <topic-connection-factory-name>TCF</topic-connection-factory-name> <topic-name>TOPLINK_CACHE.REFRESH</topic-name> <jndi-naming-service> <user-name>user</user-name> <password>password</password> <initial-context-factory-name>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory-name> </jndi-naming-service> </transport> </remote-command> <logging xsi:type="eclipselink-log"> <log-level>all</log-level> <file-name>/logs/eclipselink.log</file-name> <logging-options> <log-exception-stacktrace>true</log-exception-stacktrace> <print-thread>true</print-thread> <print-session>false</print-session> <print-connection>false</print-connection> <print-date>true</print-date> </logging-options> </logging> <primary-project xsi:type="class">ToplinkProject</primary-project> <login xsi:type="database-login"> <platform-class>org.eclipse.persistence.platform.database.oracle.Oracle10Platform</platform-class> <external-connection-pooling>true</external-connection-pooling> <external-transaction-controller>false</external-transaction-controller> <sequencing> <default-sequence xsi:type="native-sequence"> <name>Default</name> </default-sequence> </sequencing> <datasource>PoolTXDS</datasource> </login> </session> </sessions> Reproducible: Always
It would be a good idea to send this request to either the users mailing list, or post it on the newsgroup. You will get a larger group of people that can potentially help you address this issue.
I am closing this bug for now as I suspect some help on the mailing list or newsgroup is really what you need here. Please feel free to reopen if this turns out to be a bug.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink