[OSB 10.3.1] error adding a JMS destination

Hi all,
I'm migrating my ALSB 3.0 project into OSB 10.3.1. So I've recreated the clustered domain in OSB as I did with ALSB and then ready to run my
ebAdmin.cmd properties\local\admin.DVE.osb_cluster1.SYS.properties properties\local\admin.DVE.osb_cluster1.APP.properties create-jms-core
in order to create my JMS resources ... all go find excpet at the end when the script tries to activate the changes:
Buildfile: admin.xml
create-jms-core:
admin:
[java] Initializing WebLogic Scripting Tool (WLST) ...
[java] Welcome to WebLogic Server Administration Scripting Shell
[java] Type help() for help on available commands
[java] ===============================================================
[java] Loading admin properties file from : ./admin.properties
[java] ===============================================================
[java] Connecting to t3://localhost:7001 with userid weblogic ...
[java] Successfully connected to Admin Server 'AdminServer' that belongs to domain 'osb_cluster1'.
[java] Warning: An insecure protocol was used to connect to the
[java] server. To ensure on-the-wire security, the SSL port or
[java] Admin port should be used instead.
[java] Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
[java] For more help, use help(domainRuntime)
[java] Location changed to edit tree. This is a writable tree with
[java] DomainMBean as the root. To make changes you will need to start
[java] an edit session via startEdit().
[java] For more help, use help(edit)
[java] You already have an edit session in progress and hence WLST will
[java] continue with your edit session.
[java] Starting an edit session ...
[java] Started edit session, please be sure to save and activate your
[java] changes once you are done.
[java] ===============================================================
[java] Creating JMS core resources
[java] ===============================================================
[java] #### found managed: m01
[java] #### ready to create file store EventBusFileStore_m01
[java] #### created file store EventBusFileStore_m01
[java] #### ready to create JMS server EventBusJMSServer_m01
[java] #### created JMS server EventBusJMSServer_m01
[java] #### found managed: m02
[java] #### ready to create file store EventBusFileStore_m02
[java] #### created file store EventBusFileStore_m02
[java] #### ready to create JMS server EventBusJMSServer_m02
[java] #### created JMS server EventBusJMSServer_m02
[java] #### ready to create JMS module EventBusSystemModule
[java] #### created JMS module EventBusSystemModule
[java] #### ready to create connection factory EventBusConnectionFactory
[java] #### created connection factory EventBusConnectionFactory
[java] #### ready to create XA connection factory EventBusXAConnectionFactory
[java] #### created XA connection factory EventBusXAConnectionFactory
[java] #### ready to create dummyConsumerEventConsumer1OutboundQueue
[java] #### created dummyConsumerEventConsumer1OutboundQueue
[java] #### ready to create dummyConsumerEventConsumer1RecoveryOutboundQueue
[java] #### created dummyConsumerEventConsumer1RecoveryOutboundQueue
[java] #### ready to set error destination dummyConsumerEventConsumer1RecoveryOutboundQueue for dummyConsumerEventConsumer1OutboundQueue
[java] #### error destination set successfully for dummyConsumerEventConsumer1OutboundQueue
the same for other many Uniform Distributed Queues
[java] #### ready to create MonitorTopic
[java] #### created MonitorTopic
[java] Saving all your changes ...
[java] Saved all your changes successfully.
[java] Activating all your changes, this may take a while ...
[java] The edit lock associated with this edit session is released
[java] once the activation is completed.
[java] This Exception occurred at Sat Aug 15 14:12:14 CEST 2009.
[java] weblogic.application.ModuleException: ERROR: Unable to add destination EventBusSystemModule!wlsbJMSServer_auto_1@dummyConsumerEventConsumer1OutboundQueue to the back end wlsbJMSServer_auto
_1
[java] at weblogic.jms.backend.BEDestinationRuntimeDelegate.prepare(BEDestinationRuntimeDelegate.java:197)
[java] at weblogic.jms.backend.udd.UDDEntity.prepare(UDDEntity.java:444)
[java] at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1704)
[java] at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
[java] at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
[java] at weblogic.jms.module.JMSModule.prepare(JMSModule.java:277)
[java] at weblogic.jms.module.ModuleCoordinator.prepare(ModuleCoordinator.java:185)
[java] at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
[java] at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
[java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
[java] at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
[java] at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
[java] at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
[java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
[java] at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
[java] at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
[java] at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
[java] at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
[java] at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
[java] at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
[java] at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
[java] at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
[java] at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
[java] at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
[java] at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
[java] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
[java] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
[java] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
[java] at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
[java] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
[java] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[java] Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045050]A destination of name EventBusSystemModule!wlsbJMSServer_auto_1@dummyConsumerEventConsumer1OutboundQueue has a jms-create
-destination-identifier of name EventBusSystemModule!wlsbJMSServer_auto_1@dummyConsumerEventConsumer1OutboundQueue. However, another destination of name EventBusSystemModule!wlsbJMSServer_auto_1@dummy
ConsumerEventConsumer1OutboundQueue has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot be co-located on the JMSServer named wlsbJMS
Server_auto_1.
[java] at weblogic.jms.backend.BackEnd.addDestination(BackEnd.java:1527)
[java] at weblogic.jms.backend.BEDestinationRuntimeDelegate.prepare(BEDestinationRuntimeDelegate.java:195)
[java] ===============================================================
[java] #### ERROR - unexpected error: main.WLSTException
[java] ===============================================================
[java] No stack trace available.
[java] Edit session is cancelled successfully
[java] Disconnected from weblogic server: AdminServer
[java] Unexpected error: main.WLSTException
[java]
[java] Problem invoking WLST - Traceback (innermost last):
[java] File "K:\EventBus\scripts\admin.py", line 910, in ?
[java] File "K:\EventBus\scripts\admin.py", line 216, in admin
[java] File "K:\EventBus\scripts\admin.py", line 366, in configJMSCore
[java] File "K:\EventBus\scripts\admin.py", line 681, in endTransaction
[java] File "<iostream>", line 364, in activate
[java] WLSTException: Error occured while performing activate : Error while Activating changes.ERROR: Unable to add destination EventBusSystemModule!wlsbJMSServer_auto_1@dummyConsumerEventConsume
r1OutboundQueue to the back end wlsbJMSServer_auto_1 Use dumpStack() to view the full stacktrace
what I don't understand is the fact that my EventBusSystemModule in some way references wlsbJMSServer_auto_1 (not created by my script but this JMS server is already available in OSB).
I run successfully the above script againt ALSB 3.0 but now with OSB something goes wrong.
As you see from above output, the script:
- create file store EventBusFileStore_m01 (m01 is the m01 managed server in the cluster)
- create JMS server EventBusJMSServer_m01
- create file store EventBusFileStore_m02
- create JMS server EventBusJMSServer_m02
- created JMS module EventBusSystemModule
from py point of view the code is:
def createJMSModule(jmsModuleName, cluster):
print '#### ready to create JMS module ' + jmsModuleName
cd('/')
jmsModule = cmo.createJMSSystemResource(jmsModuleName)
cd('/JMSSystemResources/' + jmsModuleName)
set('Targets',jarray.array([ObjectName('com.bea:Name=' + cluster + ',Type=Cluster')], ObjectName))
print '#### created JMS module ' + jmsModuleName
print
about the creation of the UDQ
def createUniformDistributedQueue(destinationName, jndiDestination, jmsModuleName):
print '#### ready to create ' + destinationName
path = '/JMSSystemResources/' + jmsModuleName + '/JMSResource/' + jmsModuleName
try:
cd(path)
except WLSTException,e:
failed = 'Check if create-jms-core task has been already executed'
raise Failure(failed)
cmo.createUniformDistributedQueue(destinationName)
cd('/JMSSystemResources/' + jmsModuleName + '/JMSResource/' + jmsModuleName + '/UniformDistributedQueues/' + destinationName)
cmo.setJNDIName(jndiDestination)
cmo.setLoadBalancingPolicy('Round-Robin')
cmo.setDefaultTargetingEnabled(true)
print '#### created ' + destinationName
print
I'm trying to understand where is the problem ....
Thanks in advance
ferp

Sounds like the database information is wrong, Have you tried correctign this through the BPM Process administrator? There are a few places where you setup database configuration it's probably one of them.
I'm am fairly new so I can only offer up that.
I'm having a nightmare myself deplying a process engine, good luck
mARK

Similar Messages

Error when setting JMS Destination for Agile PLM Content Services (cannot

In not the right forum please suggest the correct one.
Before creating the destination I did the following setup and testing.
1.) Created a JMS on the Weblogic Server
2.) Created a Jdeveloper BPEL Project and successfully put a message into the JMS queue
Here are the details for the new destination I am creating.
1.) Protocol = JMS
2.) Provider Context Factory = weblogic.jndi.WLInitialContextFactory
* this is the one that seems to be the cause of the error
3.) Connection Factory = jmstest/jmstest-cp
* this is my JNDI name for the connection pool
4.) Default Provider URL = t3://10.16.131.110:7001
* this is the URL for the Weblogic server
5.) Destination Name = jms/queueout
* this is the JNDI name for the queue
The error message I am getting when I click the button to "Test Destination" is
"The remote server returns the following message: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory"
I would appreciate any input
Thanks

Which version of Agile are you using?
There is a patch needed for agile 9.2 for weblogic server.
Please check the Metalink

A JMS destination limit was reached.

Hi,
I encounter en error when I deploy an application under Application Server 9.
I got the following error message :
A JMS destination limit was reached. Too many Subscribers/Receivers for Queue : NewMessage user=guest, broker=localhost:7676(2832)What I need to configure / change / adapt my code ? I use the Click Framework to retrieve a Facade :
    /** Creates a new instance of Hello */
    public Hello() {
        tableToto = new Table();
        if (newsEntityFacade == null) newsEntityFacade = lookupNewEntityFacade();
        tableToto.setClass("simple");
        tableToto.setPageSize(40);
        tableToto.setName("tableToto");
        tableToto.addColumn(new Column("id"));
        tableToto.addColumn(new Column("title"));
        tableToto.addColumn(new Column("body"));
        index = 0;
        max = newsEntityFacade.count();
        rowByPage = tableToto.getPageSize();
        tableToto.setRowCount(max / rowByPage);
private NewEntityFacadeLocal lookupNewEntityFacade() {
        try {
            Context c = new InitialContext();
            return (NewEntityFacadeLocal) c.lookup("java:comp/env/ejb/NewEntityFacade");
        catch(NamingException ne) {
            Logger.getLogger(getClass().getName()).log(Level.SEVERE,"exception caught" ,ne);
            throw new RuntimeException(ne);
    }And my Facade is declared as @Stateless

I've checked that topic earlier before I have posted mine, but at that time it didn't strike me! Now, I realize the exact problem!
I need to undeploy my message-driven bean tutorial example, which was using the same queue!
Thanks.

Weblogic 8.1: Remote/Foreign Server JMS - Destination not found error

Hi
This is our current setup: Weblogic Server 8.1 with JMS module running on the same instance as the application. We would like to move JMS out into its own box. I am currently setting up my development environment to test the new setup. These are the steps I followed:
* Setup the server instance running the application on one box (Box1). Removed the existing JMS Connection Factory and Destination JNDI setup
* Setup a server instance on another box (Box2) without the application. Created the necessary JMS Connection Factories and Destinations. Started the server instance on Box2
* Added a Foreign Server configuration on Box1. Created the connection factory and destinations under this foreign server pointing to Box2
* The Foreign JNDI names are being bound correctly (I verified the JNDI tree on Box1). Restarted the server instance of Box1
Message-Driven Beans deployed on Box1 are unable to retrieve messages from Box2. The exception thrown is given below. Any help in troubleshooting and resolving this issue is appreciated.
<Warning> <EJB> <myserver> <main> <<WLS Kernel>> <> <BEA-010061> <The Message-Driven EJB: MyBean is unable to connect to the JMS destination: jms/my.application.firstQueue. The Error was:
weblogic.jms.common.JMSException: Destination not found
weblogic.jms.common.JMSException: Destination not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
at weblogic.jms.backend.BESession.createConsumer(BESession.java:153)
at weblogic.jms.backend.BESession.invoke(BESession.java:1457)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:232)
at weblogic.jms.frontend.FESession$3.run(FESession.java:1058)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1054)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2552)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1860)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1691)
at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1530)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1720)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2019)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:846)
at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1660)
at weblogic.ejb20.deployer.EJBDeployer.startMessageDrivenBeans(EJBDeployer.java:1555)
at weblogic.t3.srvr.T3Srvr.startMDBs(T3Srvr.java:948)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1024)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Edited by: user8773992 on Sep 2, 2009 11:31 AM

1 - Ensure that the MDB is configured to reference the remote connection factory AND remote destination.
2 - If using the foreign JMS server facility, ensure that it defines the URL of the remote cluster/server, a connection factory mapping, and a destination mapping. Also ensure that the MDB connection factory and destination descriptor fields reference the local JNDI names for the mappings.
3 - If not using the foreign JMS server facility, ensure that the MDB descriptor has the URL of the remote cluster, and a destination JNDI name that's in the remote cluster. (The connection factory JNDI name is not needed in this case, as the MDB will automatically look for a default connection factory that MDB's use.)
I think the MDB chapter of the EJB programmer's guide will likely be helpful here. The latest documentation for the latest release may be more up-to-date than 8.1 -- the concepts are the same with the newer releases.
Tom

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Error adding buffer entry when using Asynchronous mode of JRA and JCO call

Enviroment: XMII 12.1.4 / CE EhP1 SP03
When I using SAP JRA Function Call or SAP JCO Funciton Call in transaction, it works well when I choose 'Process Type' as 'Synchronous processing' in 'Data Buffering Configuration' tab. But when I use 'Asynchronouse processing' it doesn't work.
I check the Netweaver logs, there some logs like following:
Error adding buffer entry (com.sap.xmii.dataqueue.DataBufferManager)
Couldn't add buffer entry (com.sap.xmii.dataqueue.DataBufferManager)
ManagedConnectionImpl.dissociateConnections(), dissociation of a non-cci transaction, H1, C1(com.sap.mw.jco.jra)
how could I solve this problem?

Solved after deploy 12.1 SP05 (xMII 12.1.5 build 91)

Status 56 - IDOC with errors added

Hi everyone,
 I was configuring File to IDOC Scenario, in the receiving R/3 system, i am getting error as Status 56 - IDOC with errors added "EDI: Partner Profile not available".
 but i had already created Partner profile in WE20.
Regards,
Varun Reddy.K

Hi Varun,
 The below link will help u in solving u r problem
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Just try follow the steps followed in above mentioned link
And also check u r RFC connection in TC "SM59".
Reward with ponits if helpful
Regards
Sai Ganesh

Error in Receiver - IDoc with errors added

Hi All,
I am getting error in 56 - IDoc with errors added in receiver System.
I am new in Idoc - please tell me How to resolve this issue..
Thanks in advance..

Hi all thanks for reply .
All are the help full answer ,
I use T-code WE19 and change partner profile and execute now it is fine.
But i have checked all configuration regard partner profile from T-code WE20 it looking everything is fine but in Test tool for Idoc Processing by t-code WE19 i have checked it will taken wrong partner profile detail after giving correct manually now it is working fine.

Error adding a child form to more than one form

When I try to add a child form to more than one form, I get the following error:
Error Keyword: SDK.ADDFKCON
Description: Error Adding Foreign Key/Constraint.
Remedy:
Action: F
Severity: H
Help URL:
Detail:
The following is the log trace:
ERROR,23 nov 2011 17:22:42,050,[XELLERATE.ADAPTERS],Event: SDH Drop Foreign Constraint has encountered an error.
ERROR,23 nov 2011 17:22:54,519,[XELLERATE.DATABASE],ALTER TABLE UD_TICKET3 ADD (UD_ADUSER_KEY NUMBER(19) CONSTRAINT NN_UD_TICKET3_UD_ADUSER_KEY NOT NULL, CONSTRAINT FK_UD_TICKET3_UD_ADUSER FOREIGN KEY(UD_ADUSER_KEY) REFERENCES UD_ADUSER(UD_ADUSER_KEY))
java.sql.SQLException: ORA-01758: table must be empty to add mandatory (NOT NULL) column
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
     at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1285)
     at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1772)
     at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1741)
     at com.thortech.xl.util.JDBCUtils.executeUpdate(Unknown Source)
     at com.thortech.xl.dataaccess.tcDataBase.writeStatement(Unknown Source)
     at com.thortech.xl.dataobj.tcDataBase.writeStatement(Unknown Source)
     at com.thortech.xl.client.events.tcSDHAddForeignConstraint.createColumns(Unknown Source)
     at com.thortech.xl.client.events.tcSDHAddForeignConstraint.implementation(Unknown Source)
     at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.eventPostInsert(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
     at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
     at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Source)
     at com.thortech.xl.ejb.databeansimpl.tcSDHBean.save(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SecurityRoleInterceptor.invoke(SecurityRoleInterceptor.java:47)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:844)
     at tcSDH_RemoteProxy_6ocop18.save(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
ERROR,23 nov 2011 17:22:54,519,[XELLERATE.DATABASE],Class/Method: tcDataBase/writeStatement encounter some problems: ORA-01758: table must be empty to add mandatory (NOT NULL) column
java.sql.SQLException: ORA-01758: table must be empty to add mandatory (NOT NULL) column
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
     at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1285)
     at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1772)
     at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1741)
     at com.thortech.xl.util.JDBCUtils.executeUpdate(Unknown Source)
     at com.thortech.xl.dataaccess.tcDataBase.writeStatement(Unknown Source)
     at com.thortech.xl.dataobj.tcDataBase.writeStatement(Unknown Source)
     at com.thortech.xl.client.events.tcSDHAddForeignConstraint.createColumns(Unknown Source)
     at com.thortech.xl.client.events.tcSDHAddForeignConstraint.implementation(Unknown Source)
     at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.eventPostInsert(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
     at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
     at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Source)
     at com.thortech.xl.ejb.databeansimpl.tcSDHBean.save(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SecurityRoleInterceptor.invoke(SecurityRoleInterceptor.java:47)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:844)
     at tcSDH_RemoteProxy_6ocop18.save(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
ERROR,23 nov 2011 17:22:54,519,[XELLERATE.ADAPTERS],Event: Adding Foreign Constraint has encountered an error.
How to correct this?
Thank you!

899043 wrote:
Thanks for your reply!
I have a form named UD_TICKET3. This form contains information about the ticket number and a comment about any action taken on a resource of identity. We want to add this form as a child of all the resources forms. The problem occurs when I try to add the child form to the second form.You cannot add same detail table (child form) to more than one master table (resource form).

Duplicate MessageID error in sender JMS

Hi,
could anyone provide some inputs in getting through the following error in sender JMS:
A duplicate JMS message was received. It was was received earlier and processed with the XI message ID 3fc663bf-c3ee-4eb8-179e-ad28e0ecde3a. It will be ignored and discarded from the JMS queue.
I have tried changing follwoign settings but still no use...
Under the PROCESSING tab, under XI SETTINGS
Time period for Duplicate Check for EO(IO) (secs) it was set to 86400
I have changed this to 300 seconds
Regards,
Chinna.

remove the duplicate entry from the java table XI_AF_SVC_ID_MAP

File to JMS Scenario - Error is Receiver JMS Adapter

Hi,
I am working on File to JMS scenario. I have deployed all required jars for MQ 6.0.2 in SDM. Create all MQ related objects. I am getting following error for Receiver JMS adapter in CC Monitoring.
Please let me know if I have missed anything. Is there anything to do in Visiual Administrator->JMS Provider or JMS Connector for these kind of Scenarios?
Thanks in Advance...
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Hi,
I have made my Qmanager as default Qmgr. Now the error is :- Socket connection attempt refused
Recv JMS Communication Channel Error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Changing Time Zone (stsadm tzmove) = Error: Adding a value to a 'datetime' column caused an overflow

After updating timezone.xml и RGNLSTNG.xml files for my SharePoint 2010 (SP2 - 14.0.7015.1000)
I have to run this command to Update time zone on calendar events:
stsadm -o tzmove -name "russ2014" -update all
But this cause an error: Adding a value to a 'datetime' column caused an overflow
ULS log event: System.Data.SqlClient.SqlException: Adding a value to a 'datetime' column caused an overflow. The statement has been terminated.
How to fix this?

Hi,
Whether you added new time zone definition to your timezone.xml
and RGNLSTNG.xml files. if not, please provide the details about what content you updated in timezone.xml and RGNLSTNG.xml files.
The stsadm.exe –o tzmove command does not work for new time zone definition changes.
This command is designed for making changes in the existing time zone,
not for creating a new time zone definition.
After you modify the Timezone.xml and Regnlstng.xml files to include the new time zone definition, you must restart Internet Information Services (IIS).
To do this, click Start, click Run, type
iisreset in the Open box, and then click
OK.
Try to do IIS restart, compare the results.
Best Regards,
Lisa Chen
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Post system refresh, "Request IDoc : IDoc with errors added"

Hello All,
Post system refresh, we are not able to execute the data loads.
While loading the Infopackage, the overall status is still showing in YELLOW status. but in the Transfer (IDOCs & TRFC), it shows an Error message as "Request IDoc : IDoc with errors added"
Yesterday immediately after the refresh, we were able to execute the master data loads (full loads)...
However, transaction loads (delta) is facing issues.
Today, we are facing the problem in both master and transaction data.
Please help!!!! Its a very critical issue!!!
Edited by: Siegfried Szameitat on Aug 9, 2011 10:17 AM

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

OSB : Alert Destination not alerting on the JMS destination Topic

Hi,
I am using OSB alert destination to alert on an SLA alert of a proxy service.
The alert destnation configuration has a JMS destination of Topic type. Syntax which i followed is jms://localhost:8011/weblogic.JmsConnectionFactory/weblogic.ReportingTopic
I am able to see the alerts on the dashboard but then i cannot get the alert on topic.
I could see the below exception in log file:
Alert Rule Name: test.
com.bea.wli.sb.transports.TransportException: [JMSClientExceptions:055091]Destination JmsModule!ReportingTopic must be a queue
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:570)
     at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:681)
     at sun.reflect.GeneratedMethodAccessor1206.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy123.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:490)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
     at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
     at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:346)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:67)
     at com.bea.alsb.alert.sla.SlaAlertManager.generateAlert(SlaAlertManager.java:149)
     at com.bea.alsb.alert.sla.SlaAlertManager.access$100(SlaAlertManager.java:33)
     at com.bea.alsb.alert.sla.SlaAlertManager$RuleListenerForAlertGeneration.onRuleTrue(SlaAlertManager.java:227)
     at com.bea.alsb.rule.RuleEngine$ListenerInvocation.invokeListener(RuleEngine.java:76)
     at com.bea.alsb.rule.RuleEngine$ListenerInvocation.access$000(RuleEngine.java:61)
     at com.bea.alsb.rule.RuleEngine.addFact(RuleEngine.java:115)
     at com.bea.alsb.alert.sla.SlaAlertManager.intervalCompleted(SlaAlertManager.java:202)
     at com.bea.alsb.alert.sla.TaskCollector$RuleEvaluationTask.run(TaskCollector.java:177)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:139)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
     at java.lang.Thread.run(Thread.java:619)
In the alert destination i selected the destination type as topic. Is there anything i am missing. I checked the documentation it says that the jms destination in alert destination can be Queue/Topic. Please suggest. Thanks in advance

A topic wont persist the message, unlike a queue, if there are no subscribers attached to it currently or if there are no durable subscriptions. Create a proxy service to consume the alert from the topic and see whether you are getting it within the proxy's pipeline.

Error of Foreign JMS server connecting to durable subscriber topic

Weblogic server domain is trying to connect to the durable topic configured on the other weblogic domain. (Both domain are running on weblogic 9.2 platform)
WLI 9.2 Event generator is TestPinFJ is the MDB which is trying to listen message from Foreign JMS.
Following error we have got when I did following configuration for connecting to durable topic using foreign JMS.
<EJB> <BEA-010061> <The Message-Driven EJB: TestPinFJ is unable to connect to the JMS destination: TestQueue. The Error was:
java.lang.IllegalArgumentException: port out of range:-16>
Detail configuration is as follows:
Foreign JMS : TestFS
General:
JNDI Connection URL: t3://10.20.65.95:9004 TestClient123 (where TestClient123 is the client id for durable subscriber topic )
Destinations:
Local JNDI Name: TestQueue
Remote JNDI Name: TestTopic
Connection Factories :
Local JNDI Name: TestQCF
Remote JNDI Name: TestTCF
My suspect is the JNDI connection URL is incorrect. Please advice how to configure JNDI conn url while connecting to durable topic with client id?

hi Hussain,
I am the collegue of the person created this thread.
Thaks for the input. can u please suggest me how do we configure connectionfactory and JSM topic to durable subscription with ClientID.Shoudl th eClientID be same for JMSTopic and ConectionFactory?
In Domain "A" I have created JMS topic with durable subscriber wioth client ID "TestClient123" and created a conenctionfacory with same client ID "TestClient123" .
In Domain "B" i created a foreign JMS connecting to topic in Domain A using connection facatory created in Domain "A" configured as as remoteConnectionFActory.
Also the JNDI Connection URL is : t3://10.20.65.95:9004
"weblogic.jms.common.InvalidClientIDException: Client id, Testclient1, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
Nested exception: weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)".
weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)"
IS there any chnage i need to make to get this connectivity between Domain A and B working?
Appreciate your help on this.

[OSB 10.3.1] error adding a JMS destination

Similar Messages

Maybe you are looking for