Using weblogic repository of message beans

Hi,
Using weblogic repository of message beans
This is possible?

Hi Steve,
I don't know what you need UOO for, but, for some use cases, its sufficient just to configure a default UOO on the sender's connection factory.
Propapagation of a UOO from one desitnation to another is not automatic (except via SAF, or unless OSB somehow does it for you). Plain vanilla JMS apps do this by calling msg.getStringProperty("JMS_BEA_UnitOfOrder") on the received message and setUnitOfOrder() on the javax.jms.WLProducer.
You might find that there's more OSB expertise on an OSB newsgroup (I think it's one of the newsgroups under [url http://forums.oracle.com/forums/category.jspa?categoryID=194]SOA & Process Management).
Regards,
Tom

Similar Messages

Can I use oracle blob by CMP bean in weblogic 6?

I use weblogic 6.1(sp3) and Jbuilder 7.when I try to use oracle blob by CMP bean,the
errors are:
javax.ejb.FinderException: Exception raised in findByPrimaryKey
java.io.StreamCorruptedException: InputStream does not contain a serialized object
What should I do?Is there examples about using oracle blob?
thanks a lot!

Great! So what was the problem?
Regards,
Slava Imeshev
"Roger Lee" <[email protected]> wrote in message
news:[email protected]...
>
Finally got it working with CMP, which is my preferred choice (over BMP).
I read the Excel Spreadsheet into a "byte []" array, and the Entity Beanmapped
"byte []" to the Blob column in the Oracle table.
"Slava Imeshev" <[email protected]> wrote:
Roger,
I'm not quite sure I undestand the problem. Could you:
1. Post deployment descriptors in part related to this
CMP bean?
2. Post the piece of code that is failing?
Please post the information above and we will help
you to hunt the problem down.
No, I don't have any problems accessing blobs
from CMP.
Regards,
Slava Imeshev
"Roger Lee" <[email protected]> wrote in message
news:[email protected]...
Yes. I have added;
<dbms_column-type>OracleBlob</dbms-column-type>
It fails because the locater to the blob, obtained by findBYPrimaryKeyis
null.
i.e. an empty_blob() is not created.
Have you got CMP to access Blobs in WLS 6.1?
"Slava Imeshev" <[email protected]> wrote:
Hi Roger,
Have you tried using OracleBlob as dbms-column-type?
Also, could you post that part of your code that is failing?
Regards,
Slava Imeshev
"Roger Lee" <[email protected]> wrote in message
news:[email protected]...
I can access Clobs using CMP. If you are using the Oracle OCI Driveryou
do not
need to add this line.
However if you are using the Oracle Type 4 Thin drivers you need
to
add;
<dbms_column-type>OracleClob</dbms-column-type>
to the file;
weblogic-cmp-rdbms-jar-xml
This DOES NOT work with Blobs.
I am unable to get WebLogic 6.1 sp4 persist a Blob to an Oracle
8.1.x
table and
retrieve it using either CMP or BMP.
Unless any one show me a complete working CMP and BMP example?
Roger Lee
Deepak Vohra <[email protected]> wrote:
BLOB and CLOB DBMS Column Support for the Oracle DBMS
http://edocs.bea.com/wls/docs61/ejb/cmp.html#1061636
shybird wrote:
I use weblogic 6.1(sp3) and Jbuilder 7.when I try to use oracle
blob
by CMP bean,the
errors are:
javax.ejb.FinderException: Exception raised in findByPrimaryKey
java.io.StreamCorruptedException: InputStream does not contain
a
serialized
object
What should I do?Is there examples about using oracle blob?
thanks a lot!

How to stop reading foreign queue message from MDB using weblogic 6.1? thanks,

Hi, I am using weblogic 6.1 to communicate with IBM MQseries foreign
queue. I use the asychronous way "onMessage()"(properly the only
known way) to listen the messages from the queue. I like to stop
receiving messages if my south bound stream has problems and not able
to process the message, I would like to stop fetching the message with
my MDB(message driven bean) untill the down stream problem is cleared.
As weblogic uses container to create the multiple session and
connections internally, how can I efficiently stop the message
delivery, do I have to locate all the connections and issue
connection.stop()for each one, or there is better way to do this.
Thanks in advance.

If you never use FaceTime on your Mac, open the FaceTime app on it and sign out. Also, the following instructions are from Connect your iPhone, iPad, iPod touch, and Mac using Continuity - Apple Support
Turn off iPhone cellular calls
To turn off iPhone cellular calls on your iPad or iPod touch, go to Settings > FaceTime and turn off iPhone Cellular Calls.
On your Mac, open the FaceTime app and go to FaceTime > Preferences. Click Settings and deselect the iPhone Cellular Calls option.

Message redelivery with non-transactional message bean JMS standard or weblogic standard?

It is my understanding (or maybe my assumption) that a message is
          re-queued only if the transaction attribute of a container-managed
          message bean is set to "Required" and the message is PERSISTENT. So if
          it's set to "NotSupported", and thus, message receival is not within a
          transaction, the message would be un-queued and thus never be
          redelivered, should a failure occur within the bean. I discovered that
          even if the message bean is set as "NotSupported", should a failure
          occur within the bean, the message is re-queued to be received again
          at a later time.
          I'm very confused as to whether this mechanism is a JMS standard, or a
          feature of Weblogic. Well, maybe I'm just confused about message
          delivery/re-delivery. I understand that the JMS standard requires
          guaranteed delivery of a message to a receiver. Does this mean a
          message is only considered delivered if an acknowledgement is
          received, regardless of the transaction level? In other words, is the
          JMS standard that a message is considered delivered only if
          acknowledgement is indicated through the container, regardless of the
          transaction level of the message bean itself?


You're right on the second part. That is, a JMS message is not considered to
          be "delivered" until it is acknowledged. There are a number of ways to make
          this happen when programming to the raw JMS API -- a look at the Javadoc for
          JMS or a good JMS book should clarify how to do this.
          With a message-driven bean, the EJB container acknowledges the message after
          you've successfully returned from the "onMessage" method. If you throw a
          RuntimeException from the "onMessage" method, or if it's an MDB with a
          transaction mode of "Required" and you call "setRollbackOnly" on the
          "MessageDrivenContext" object -- then your message will be redelivered.
          Regardless of how a message is acknowledged, if it's not acknowledged then
          it will be redelivered. This has nothing to do with whether the message is
          persistent. The difference is that if a message is persistent, then the JMS
          server is required to keep a copy on stable storage until the message is
          acknowledged so that if the JMS server itself crashes, the message will not
          be lost. For a non-persistent message, on the other hand, if the JMS server
          crashes, then the message may be lost.
          greg
          "Justin" <[email protected]> wrote in message
          news:[email protected]...
          > It is my understanding (or maybe my assumption) that a message is
          > re-queued only if the transaction attribute of a container-managed
          > message bean is set to "Required" and the message is PERSISTENT. So if
          > it's set to "NotSupported", and thus, message receival is not within a
          > transaction, the message would be un-queued and thus never be
          > redelivered, should a failure occur within the bean. I discovered that
          > even if the message bean is set as "NotSupported", should a failure
          > occur within the bean, the message is re-queued to be received again
          > at a later time.
          >
          > I'm very confused as to whether this mechanism is a JMS standard, or a
          > feature of Weblogic. Well, maybe I'm just confused about message
          > delivery/re-delivery. I understand that the JMS standard requires
          > guaranteed delivery of a message to a receiver. Does this mean a
          > message is only considered delivered if an acknowledgement is
          > received, regardless of the transaction level? In other words, is the
          > JMS standard that a message is considered delivered only if
          > acknowledgement is indicated through the container, regardless of the
          > transaction level of the message bean itself?

B2B using JMS and Processing Messages with Message Driven Beans

We want to be able to use B2B to send messages to a JMS queue and then process messages from B2B using a Message Driven Bean. Is this supported.
We are using B2B 10.2.0.2 with Patchset 4.

Hello,
In 10.1.2.0.2 B2B , as part of the internal Delivery channel B2B can only send and receive messages from JMS queues.
Rgds,Ramesh

Message bean does not start automatically during application server startup

I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                ... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                at java.lang.Class.getDeclaredConstructors0(Native Method)
                at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                at java.lang.Class.getConstructor0(Class.java:1930)
                at java.lang.Class.newInstance0(Class.java:278)
                at java.lang.Class.newInstance(Class.java:261)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.Subject.doAs(Subject.java:379)
                at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve

Help!.... XA error: using Weblogic 6.1 and Oracle 8.1.6

          Hi,
          I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
          to use Container Managed Transaction through a Session Bean.
          Connection Pool Settings: -------------------------
          Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
          TXDataSource Settings : -----------------------
          Name - myXADS
          JNDIName - myXADS
          PoolName - myXAPool
          Everything works fine but once in a while I get the following exception:
          java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
          in the transaction branch start() failed on resource 'myXAPool' Unexpected error
          during start for XAResource 'myXAPool': null
          The connection pool size is 30 and the number connections high reached was 5,
          which means there are enough connections in the pool available at all time.
          It would be really great if you can help me out.
          Thanks in Advance, Sudhir.


Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

XA error: using Weblogic 6.1 and Oracle 8.1.6

Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
in the transaction branch start() failed on resource 'myXAPool' Unexpected error
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reached was 5,
which means there are enough connections in the pool available at all time.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

Error when using weblogic portal 10.3.5

Hi, everyone.
- I'm using weblogic portal 10.3.2 to develop a portal. Now, i deploy my project for customer but they want to deploy it in Centos OS.
- I down load weblogic portal form oracle site but it don't have 10.3.2 version. I use the latest version oracle weblogic portal 10.3.5 but when run my project it has error:
com.bea.content.AuthenticationException: Error authenticating to repository: WLP. Possible cause could include, but is not limited to a bad repository configuration or the repository is unknown. Error message: java.lang.IllegalMonitorStateException
- Can anyone help me the link down load oracle weblogic portal 10.3.2 for linux or help me resolve this error.
Thank a lot!

Hi..
They changed a few things in 10.3.. see http://edocs.bea.com/common/docs103/install/silent.html#wp1044118
looks like the Server sub category has changed to Core Application Server..
If you checkout the log.txt file in the logs directory of the root where you've installed a copy using the gui, it generally lists all the installation options available.
..Mark.

Using Weblogic app environment in Visual Age

Hi,
          I am using Weblogic as my test environment in Visual Age. I am getting alone
          well with servlet and beans. But I am having enormous problem with jsp. Does
          any body know how to configure weblogic test environment in Visual age to
          use bean tag in JSP (the JSP cannot locate the beans although the classpath
          has set to the project_resource/project Name).
          Help will be highly appreciated
          Duke


"Michael Girdley" <[email protected]> wrote in message
          news:396a80d4$[email protected]..
          > JSP integration is not supported with Weblogic and VisualAge. This is
          > because VisualAge supports a back level revision of the JSP specification
          > and has also created their JSP container to be tightly integrated with
          > VisualAge.
          I don't understand this at all.
          My VisualAge has no notion of JSP (professional), that all came after I
          imported all of
          the weblogic stuff. So what does "VA supports a back level revision of JSP
          spec" actually
          mean?
          Also, "has created their JSP container to be tightly integrated with VA".
          There is no
          JSP container to speak of except for that which weblogic provides. Perhaps
          you are
          referring to some Websphere/VA environment?
          All in all, the integration is just about wonderful. Is there a good reason
          why JSP is not
          supported? Seeing what VA does with the WebSphere environment, I believe
          that the IDE
          environment is capable of dynamically reloading classes that have been
          generated etc.
          The basic question is: Why doesn't the VA environment support JSP's? If the
          answer is:
          "we haven't implemented it yet" then I understand, (and will ask when it
          will be:-) ).
          Questioningly,
          Jon

Errors using weblogic sql driver: "No JDBC connection can be made because the transaction state is marked rollback"

One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
     at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)
     at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
     at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
     at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixin

Joseph Weinstein <[email protected]> wrote:
>
>
YuanHui Liu wrote:
Joe,
We got the exact same error message. The error came after we got theJDBC connection,
and trying to create statement off it.
It occurs intermitently when we are running another standalone JAVAapp to do
some end of day work, which results in the DB Server being very busy(90+%CPU
usage) for about 5 minutes. We see a surge of requests to the WLSJDBC Connection
pool. This would sometimes result in all our subsequent DB requeststo fail and
lead to a crash.
We are using WLS6.0SP1. I do not think there's a 30 seconds wait leadingto a
connection timeout that caused this(rather it is the end effect).
Can you give us a more detailed explanation? Is there a miscommunicationbetween
our DB(Sybase12) and WLS?Hi. It looks to you like it's after you get the connection, but really
it's when the server is
gettng the pool connection. For performance/synchronization reasons we
do a clever
delay: When your code asks for a pool connection we quickly give you
the pool wrapper,
but we delay actually reserving the real underlying DBMS connection until
your first
real need for a connection, at your first JDBC call, such as createStatement()
etc.
It is while waiting for a pool connection long enough for the transaction
coordinator
to have timed you out before you ever get a chance. It's nothing to do
with the
DBMS or even JDBC, I believe. I think the weblogic server either has
too few execute-threads
and/or too few CPU cycles to do the work load.
Okay, so there's a lazy initialization of the connection.
From reading our log I believe our failur is immediate rather
than waiting for 30+ seconds(the default setting) from the DB,
the timeout occurred later as a result. At the time either because the DB Server
is very busy.
Since we are running WLS6.0 we have only one connection pool,
we have defined a max of 150 threads in the pool. While this
is happening the DB Server is being pinned by an overnight job,
but the WLS Server is not busy at all. The DB and WLS resides
on different physical boxes.
We also have a thread dump from the WLS console when we rebooted the server, it
showed that we are hanging on to the thread & jdbc
connections after these exceptions has occurred instead of releasing them, note
"16083"(~4.5 hours) seconds has passed:
142 116222 Retry rollback request for tx: 'transaction=(IdHash=2963855,Name =
[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()],Xid=30643:8f3838f3709bf53d,Status=Rolling
Back. [Reason = Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
begin=16083,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=server),SCInfo[server]=(state=active),properties=({weblogic.jdbc=t3://159.55.158.25:8005,
weblogic.transaction.name=[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()]}))'
Scheduled Trigger
So I would argue this problem actually chewed up resources on the WLS server.
-Yuanhui Liu
>>
>>
Thanks.
-YuanHui Liu
Joseph Weinstein <[email protected]> wrote:
lixin wrote:
One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)Hi. This sounds like a JVM thread starvation issue, and/or a server
load
issue. What is
happening is that the transaction is started, and times out beforethe
SSB even gets to
the first JDBC work. I would first verify that the customer is using
the very latest JVM
available for the machine.
Joe Weinstein
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixin

SetRollbackOnly causes exception in message bean

          Hi,
          I use WebLogic Server 8.1, MDB technology and MQSeries 5.3.
          I deployed a MDB with a Container-managed transaction configuration and a XA MQ
          QCF.
          This MDB calls another EJB Session (which uses Container-managed transaction to)
          and then sends a JMS message to MQ.
          If I do an explicit rollback in the called method of the EJB Session (ctx.setRollbackOnly()),
          I have the following JMSException.
          Is it normal is it bug?
          Thanks for help
          Charles
          javax.jms.JMSException: [J2EE:160049]An error occurred while registering the JMS
          connection with JTA: weblogic.transaction.RollbackException: Unknown reason -
          with nested exception:
          [weblogic.transaction.internal.AppSetRollbackOnlyException]
          at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:29)
          at weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(WrappedTransactionalSession.java:176)
          at weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.java:124)
          at ft.services.messageOrder.MessageOrderBean.sendJMSMessage(MessageOrderBean.java:225)
          at ft.services.messageOrder.MessageOrderBean.onMessage(MessageOrderBean.java:177)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:308)
          at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:277)
          at weblogic.ejb20.internal.JMSMessagePoller.pollForAWhile(JMSMessagePoller.java:391)
          at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:435)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
          weblogic.transaction.internal.AppSetRollbackOnlyException
          at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:504)
          at weblogic.ejb20.internal.BaseEJBContext.setRollbackOnly(BaseEJBContext.java:350)
          at ft.services.order.OrderBean.putOrderRollback(OrderBean.java:138)
          at ft.services.order.Order_cpl9bk_ELOImpl.putOrderRollback(Order_cpl9bk_ELOImpl.java:315)
          at ft.services.messageOrder.MessageOrderBean.onMessage(MessageOrderBean.java:173)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:308)
          at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:277)
          at weblogic.ejb20.internal.JMSMessagePoller.pollForAWhile(JMSMessagePoller.java:391)
          at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:435)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
          --------------- nested within: ------------------
          weblogic.transaction.RollbackException: Unknown reason - with nested exception:
          [weblogic.transaction.internal.AppSetRollbackOnlyException]
          at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1644)
          at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:396)
          at weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(WrappedTransactionalSession.java:167)
          at weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.java:124)
          at ft.services.messageOrder.MessageOrderBean.sendJMSMessage(MessageOrderBean.java:225)
          at ft.services.messageOrder.MessageOrderBean.onMessage(MessageOrderBean.java:177)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:308)
          at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:277)
          at weblogic.ejb20.internal.JMSMessagePoller.pollForAWhile(JMSMessagePoller.java:391)
          at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:435)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)


Hi Charles,
          Your bean has explicitly rolled back the tx,
          this means that any operation involved in the tx
          will fail at some point, even if the operation is
          invoked after the tx is rolled back.
          If an operation is invoked for a tx that
          is already rolled back, it is up to the vendor whether
          to fail the operation by throwing an exception, or to
          fail the operation by silently rolling back the operation.
          Where the former behavior is generally considered to
          be more "helpful".
          Seems normal to me.
          Tom
          Charles Desmoulins wrote:
          > Hi,
          >
          > I use WebLogic Server 8.1, MDB technology and MQSeries 5.3.
          >
          > I deployed a MDB with a Container-managed transaction configuration and a XA MQ
          > QCF.
          > This MDB calls another EJB Session (which uses Container-managed transaction to)
          > and then sends a JMS message to MQ.
          >
          > If I do an explicit rollback in the called method of the EJB Session (ctx.setRollbackOnly()),
          > I have the following JMSException.
          >
          > Is it normal is it bug?
          >
          > Thanks for help
          > Charles
          >
          > javax.jms.JMSException: [J2EE:160049]An error occurred while registering the JMS
          > connection with JTA: weblogic.transaction.RollbackException: Unknown reason -
          > with nested exception:
          > [weblogic.transaction.internal.AppSetRollbackOnlyException]
          > at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:29)
          > at weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(WrappedTransactionalSession.java:176)
          > at weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.java:124)
          > at ft.services.messageOrder.MessageOrderBean.sendJMSMessage(MessageOrderBean.java:225)
          > at ft.services.messageOrder.MessageOrderBean.onMessage(MessageOrderBean.java:177)
          > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:308)
          > at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:277)
          > at weblogic.ejb20.internal.JMSMessagePoller.pollForAWhile(JMSMessagePoller.java:391)
          > at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:435)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
          > weblogic.transaction.internal.AppSetRollbackOnlyException
          > at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:504)
          > at weblogic.ejb20.internal.BaseEJBContext.setRollbackOnly(BaseEJBContext.java:350)
          > at ft.services.order.OrderBean.putOrderRollback(OrderBean.java:138)
          > at ft.services.order.Order_cpl9bk_ELOImpl.putOrderRollback(Order_cpl9bk_ELOImpl.java:315)
          > at ft.services.messageOrder.MessageOrderBean.onMessage(MessageOrderBean.java:173)
          > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:308)
          > at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:277)
          > at weblogic.ejb20.internal.JMSMessagePoller.pollForAWhile(JMSMessagePoller.java:391)
          > at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:435)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
          > --------------- nested within: ------------------
          > weblogic.transaction.RollbackException: Unknown reason - with nested exception:
          > [weblogic.transaction.internal.AppSetRollbackOnlyException]
          > at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1644)
          > at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:396)
          > at weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(WrappedTransactionalSession.java:167)
          > at weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.java:124)
          > at ft.services.messageOrder.MessageOrderBean.sendJMSMessage(MessageOrderBean.java:225)
          > at ft.services.messageOrder.MessageOrderBean.onMessage(MessageOrderBean.java:177)
          > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:308)
          > at weblogic.ejb20.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:277)
          > at weblogic.ejb20.internal.JMSMessagePoller.pollForAWhile(JMSMessagePoller.java:391)
          > at weblogic.ejb20.internal.JMSMessagePoller.execute(JMSMessagePoller.java:435)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
          >

Using weblogic.logging.NonCatalogLogger

I am getting an exception whenever i try to use the NonCatalogLogger.info(string,
throwable). It's a null pointer exception which is caused as the constructor of
the NonCatalogLogger seems to be returning a null object.
How do you appropriately construct a NonCatalogLogger object
weblogic.logging.NonCatalogLogger

this seems wierd ? i don't see how this constructor can return null ?
are you seeing any error in the server error log.
"Prakash M" <[email protected]> wrote in message
news:3ad216ac$[email protected]..
>
I actually changed this to a valid subsystem name; EJB; however i am stillgetting
the same exception. What can cause this ?
I am trying to use the logging API within the server instance; i.e.currently
i am trying to use it within a Message Driven Bean
Prakash
"Prakash M" <[email protected]> wrote:
My constructor is returning a null; this is caused since i do not have
a valid
subsytem name. How do i create a user-defined subsystem within WLS 6.0
Prakash
"Sanjeev Chopra" <[email protected]> wrote:
There is only 1 constructor, which takes a subsystem name (string).
This can be created only within a T3Client.
Is the constructor throwing an exception ? (if yes pls post your
stacktrace)
OR is it silently returning null.
"Prakash M" <[email protected]> wrote in message
news:3ace4899$[email protected]..
I am getting an exception whenever i try to use theNonCatalogLogger.info(string,
throwable). It's a null pointer exception which is caused as theconstructor of
the NonCatalogLogger seems to be returning a null object.
How do you appropriately construct a NonCatalogLogger object
weblogic.logging.NonCatalogLogger

I am getting build error while using weblogic.appc

Hi All,
I am using weblogic 10 server and ejb 3.0 code .
While ejb-complisation i am getting the class not found error.
Please help me in resolving the below issue.
ejb-compile:
[echo] E:\workspace\OMGAdmin\OMGADMIN/omgAdminBuild/omgAdminEAR
[java] Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/descriptor/BeanUpdateListener
[java] at java.lang.ClassLoader.defineClass1(Native Method)
[java] at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
[java] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
[java] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
[java] at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
[java] at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
[java] at java.security.AccessController.doPrivileged(Native Method)
[java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[java] at java.lang.Class.forName0(Native Method)
[java] at java.lang.Class.forName(Class.java:164)
[java] at weblogic.logging.MessageLogger.<clinit>(MessageLogger.java:46)
[java] at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:51)
[java] at weblogic.j2ee.J2EELogger.logAppcFailedWithError(J2EELogger.java:5257)
[java] at weblogic.application.compiler.Appc.runBody(Appc.java:179)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[java] at weblogic.application.compiler.Appc.main(Appc.java:188)
[java] at weblogic.appc.main(appc.java:14)
[java] Java Result: 1
<target name="ejb-compile" depends="ejb-jar">
     <echo message="${project.EAR.dir}"></echo>
     <java classname="weblogic.appc" fork="yes">
<sysproperty key="weblogic.home" value="${wl.home}"/>
<arg line="-compiler javac ${project.EJB.dir}/omgAdminEJB.jar"/>
<classpath>
<pathelement location="${wl.dir.lib}\weblogic.jar"/>
<pathelement location="${wl.dir.lib}\api.jar"/>
<pathelement location="${wl.dir.lib}\wls-api.jar"/>
          <pathelement location="${project.EAR.dir}\utility.jar"/>
          <pathelement location="${project.lib}\log4j-1.2.13.jar"/>
</classpath>
</java>
     <copy todir="${project.EAR.dir}" >
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar" />
</copy>
     <delete>
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar"/>
</delete>
</target>
above script is my ant task for ejb compilisation
Regd's
Soma.

Finally i am end up with this exception
[java] Exception in thread "main" java.lang.AssertionError: java.lang.reflect.InvocationTargetException
[java] at weblogic.logging.MessageLogger.log(MessageLogger.java:104)
[java] at weblogic.logging.MessageLogger.log(MessageLogger.java:116)
[java] at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:51)
[java] at weblogic.j2ee.J2EELogger.logAppcFailedWithError(J2EELogger.java:5257)
[java] at weblogic.application.compiler.Appc.runBody(Appc.java:179)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[java] at weblogic.application.compiler.Appc.main(Appc.java:188)
[java] at weblogic.appc.main(appc.java:14)
[java] Caused by: java.lang.reflect.InvocationTargetException
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at weblogic.logging.MessageLogger.log(MessageLogger.java:101)
[java] ... 8 more
[java] Caused by: java.lang.NoClassDefFoundError: weblogic/management/DistributedManagementException
[java] at java.lang.Class.getDeclaredMethods0(Native Method)
[java] at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2488)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2498)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2498)
[java] at java.lang.Class.privateGetPublicMethods(Class.java:2498)
[java] at java.lang.Class.getMethods(Class.java:1406)
[java] at weblogic.kernel.MBeanStub.initializeFromSystemProperties(MBeanStub.java:51)
[java] at weblogic.kernel.LogMBeanStub.<init>(LogMBeanStub.java:41)
[java] at weblogic.kernel.KernelMBeanStub.<init>(KernelMBeanStub.java:10)
[java] at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:22)
[java] at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:28)
[java] ... 13 more
[java] Java Result: 1
My Build file is
<target name="ejb-compile" depends="ejb-jar">
     <echo message="${project.EAR.dir}"></echo>
     <echo message="${wl.modules.lib}\com.bea.core.descriptor_1.0.1.0.jar" />
     <echo message="${wl.dir.lib}\weblogic.jar" />
     <java classname="weblogic.appc" fork="yes">
<sysproperty key="weblogic.home" value="${wl.home}"/>
<arg line="-compiler javac ${project.EJB.dir}/omgAdminEJB.jar"/>
<classpath>
<pathelement location="${wl.dir.lib}\weblogic.jar"/>
<pathelement location="${wl.dir.lib}\api.jar"/>
<pathelement location="${wl.dir.lib}\wls-api.jar"/>
<pathelement location="${wl.dir.lib}\wlclient.jar"/>
<pathelement location="${wl.modules.lib}\com.bea.core.descriptor_1.0.1.0.jar"/>
          <pathelement location="${project.EAR.dir}\utility.jar"/>
          <pathelement location="${project.lib}\log4j-1.2.13.jar"/>
</classpath>
</java>
     <copy todir="${project.EAR.dir}" >
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar" />
</copy>
     <delete>
<fileset dir="${project.EJB.dir}" includes="omgAdminEJB.jar"/>
</delete>
</target>

Error while trying a simple message bean

I got an error while trying the simple message bean from "Developing Enterprise Applications Using the j2ee platform" tutorial (lesson 4).
The following is the error after I clicked on submit button in bonus html:
javax.servlet.ServletException: Could not initialize due to javax.security.auth.login.FailedLoginException: Password Incorrect
     at bonus.controllers.BonusCalculationServlet.init(BonusCalculationServlet.java:81)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:852)
     at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:615)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:368)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
     at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
     at java.lang.Thread.run(Thread.java:479)
Does anybody know what cause this error? and how to solve it. Any help is very much appreciated.
Thanks in advance
Hans

I have the exact same problem.
I can't find a username/password setup for JMS.
Is the example broken?

Using weblogic repository of message beans

Similar Messages

Maybe you are looking for