DataSource unavailable

Hello,
I deployed a web app into weblogic, but unable to reach the datasource.
The web application has a web.xml and has the following resource configuration

<resource-ref id="STPResourceRef_1">
<res-ref-name>STPDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
The weblogic is configured with the following Data Source.
Data Sources
Name : STPDataSource
Type :Generic
JNDI Name : jdbc/STPStoreDataSource
Targets : myserver, Server-0
The JNDI tree has the following entry
JNDI Tree Structure
Server-0
__WL_GlobalJavaApp
java:global
javax
jdbc
STPStoreDataSource
weblogic
And the jndi entry for jdbc/STPStoreDataSource is
Binding Name: jdbc.STPStoreDataSource
Class: weblogic.jdbc.common.internal.RmiDataSource_1211_WLStub
The error I recieve in the server-0.out is
com.anitesolutions.utils.servlet.config.ConfigDatabaseException: Configuration Error: Datasource undefined - 'STPDataSource'
The same code works in websphere, but not in weblogic. I tested the Datasource in weblogic if it connects to the DB and it does. The problem is the container is unable to reach the DataSource. I can't figure out what is wrong.
Your suggestion will be useful.
Thanks

Hello,
I have got a hint. I am migrating an application in Websphere to Weblogic. In Websphere, ibm-web-bnd.xml file handles the binding between the project resource name and the datasource in websphere. The id="STPResourceRef_1" mentioned above is resolved to jdbc/STPStoreDataSource in ibm-web-bnd.xml . The code continues to use ctx.lookup("STPDataSource"). Is there any such binding in Java EE 6 or weblogic specific files? If you can tell me this missing link, my problem will be solved.

Similar Messages

DataSource Unavailable ..on console but application is fine....

Last week one of our Data bases was down for a while when some servers which use this DB in their Data sources were bouncing......so the servers would go into ADMIN mode ...i just pushed them to RUNNING mode and after a while the DB was back up ....when i checked the console there was no indication that the DS was running on that server now....but when i checked the front end application ..it was all working...that is the functionality which uses the DS was working......
Doesn't the console automatically update when the DB is back up and the DS is working???.........After bouncing the servers again ...the console indicated the DS was running.....Is this a console problem or is this how its supposed to work.....

Appreciate your response....how ever my question was .....when the DB is back up and DS is functioning (verified from front end) still the console didn't reflect the availability of the DS....but after a few hours(12-13 hrs) when the servers bounced the console was updated....(our servers cron bounce daily in the night --due to some application specific reasons)....So again my question is "Is the console supposed to be updated with the state of the DS when it becomes available...."

Help in collecting objects for transport into Q

Hi All,
We have our Q environment ready and need to transport the data flows into Q. I know that we have to replicate the datasources in Q before doing any transports. I have a flow like below:
R/3 -> ODS -> Cube. I have generated an export datasource on the ODS and created a datamrt infopackage to load from ODS to Cube. What is the correct way to collect them in transports. I read(in some of the earlier posts) that we need to transport the export datasource before transporting the Cube.
Please suggest!!!
Thanks,
RPK.

Hi,
If you are using Version 7 , no need to worry about it. We can combine both ODS and CUBE with Dataflow before and after in a transport requet.
But If I remember correctly, I had a datasource unavailability problem with both ODS and CUBE with Dataflow before and after in a transport requet in older versions.
So, in older versions, Take ODS with DFBefore in a request , trnasport and import it first, Then Replicate teh data sources from teh context menu of self source system. And then take Cube in another request with DFB and DFAfter .Import it later.
With rgds,
Anil Kumar Sharma .P

Error occured during extraction

Hello Experts,
I am using datasource 0HR_PY_PP_1 to load data into DSO 0PY_PP_C1.while loading data into DSO, I was getting error.
When I checked data in extractor for 0HR_PY_PP_1, I got error messange "Errors occurred during the extraction"
what would be an issue? do i need to do any setup before extracting data from extractor.
Regards,
Nirav Shah

HI,
Actually the data source you are talking about have some functional intricacies concerned with it , so if you could go through the below link for more information on it.
[http://sap.ittoolbox.com/groups/technical-functional/sap-bw/extraction-error-for-0hr_py_pp_1-1376478]
Check weather a valid source system exist for the concerned extractor RSA13 (Monitor icon), try replicating the data source again for the possible error conditions include specification of DataSources unavailable in the source system and changes in the DataSource setup or the extraction process that have not yet been replicated to the SAP BW system.
Extractor checker will only let you check for the extraction of specific values in rsa3, try reactivating the extractor or check "For the short dump error if any" may be there is an "Enhancement of data source " while the extractor is not properly activated.
Hope this will be expedite.
Thax & Regards
Vaibhave Sharma

R/3 extraction in to bw

Hi all
could you tell me what are the steps of R/3 extraction into BW.
Thanks

Hi,
SAP Data Extraction Steps
The following is a sample step-by-step data extraction control flow for SAP systems:
   1. An InfoPackage is scheduled for execution at a specific point of time or for a certain system- or user-defined event.
   2. Once the defined point of time is reached, the SAP BW system starts a batch job that sends a request IDoc to the SAP source system.
   3. The request IDoc arrives in the source system and is processed by the IDoc dispatcher, which calls the BI Service API to process the request.
   4. The BI Service API checks the request for technical consistency. Possible error conditions include specification of DataSources unavailable in the source system and changes in the DataSource setup or the extraction process that have not yet been replicated to the SAP BW system.
   5. The BI Service API calls the extractor in initialization mode to allow for extractor-specific initializations before actually starting the extraction process. The generic extractor, for example, opens an SQL cursor based on the specified DataSource and selection criteria.
   6. The BI Service API calls the extractor in extraction mode. One data package per call is returned to the BI Service API, and customer exits are called for possible enhancements. The extractor takes care of splitting the complete result set into data packages according to the IDoc control parameters. The BI Service API continues to call the extractor until no more data can be fetched.
   7. The BI Service API finally sends a final status IDoc notifying the target system that request processing has finished (successfully or with errors specified in the status IDoc).
Thanks,
Shankar

Data extraction for BW/BI

Hi ,
I am new in BW.Can anyone send me material on DATA EXTRACTION IN BW? I mainly want the material for LO-extraction.If anyone could provide the material on extractors like LO-cockpit,Generic data source etc.I will be really thankful.Please send the material at "baljinder4u_gmail.com" .
Thanks in advance

Hi Rakesh
Step-by-step control flow for a successful data extraction with SAP BW:
   1. An InfoPackage is scheduled for execution at a specific point of time or for a certain system- or user-defined event.
   2. Once the defined point of time is reached, the SAP BW system starts a batch job that sends a request IDoc to the SAP source system.
   3. The request IDoc arrives in the source system and is processed by the IDoc dispatcher, which calls the BI Service API to process the request.
   4. The BI Service API checks the request for technical consistency. Possible error conditions include specification of DataSources unavailable in the source system and changes in the DataSource setup or the extraction process that have not yet been replicated to the SAP BW system.
   5. The BI Service API calls the extractor in initialization mode to allow for extractor-specific initializations before actually starting the extraction process. The generic extractor, for example, opens an SQL cursor based on the specified DataSource and selection criteria.
   6. The BI Service API calls the extractor in extraction mode. One data package per call is returned to the BI Service API, and customer exits are called for possible enhancements. The extractor takes care of splitting the complete result set into data packages according to the IDoc control parameters. The BI Service API continues to call the extractor until no more data can be fetched.
   7. The BI Service API finally sends a final status IDoc notifying the target system that request processing has finished (successfully or with errors specified in the status IDoc).
Note
Control parameters specify the frequency of intermediate status IDocs, the maximum size (either in kilobytes or number of lines) of each individual data package, the maximum number of parallel processes for data transfer, and the name of the application server to run the extraction process on.
*Here is LO Cockpit Step By Step*
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
please follow the link
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=dataEXTRACTIONIN+BW&cat=sdn_all
Regards
Tapashi
Edited by: Tapashi Saha on Aug 18, 2008 11:03 AM

Weblogic datasource - Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.

I am performing some transactions with java application deployed on weblogic. I faced some issue of getting the transaction response with some delay. I found these below mention messages logged into the managed server logs.
Following is my datasource settings
Initial Capacity: 2
Maximum Capacity: 100
Capacity Increment: 20
Anyone have idea why these following errors coming.
####<Nov 26, 2013 2:25:41 PM PKT> <Info> <Common> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <BEA1-1B6BE1217D118A188C49> <> <1385457941513> <BEA-000628> <Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.>
####<Nov 26, 2013 2:25:42 PM PKT> <Info> <Common> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <BEA1-1B6EE1217D118A188C49> <> <1385457942413> <BEA-000628> <Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.>
####<Nov 26, 2013 2:25:43 PM PKT> <Info> <Common> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <BEA1-1B71E1217D118A188C49> <> <1385457943792> <BEA-000628> <Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748433> <BEA-001128> <Connection for pool "DataSource" closed.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748433> <BEA-001128> <Connection for pool "DataSource" closed.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748433> <BEA-001128> <Connection for pool "DataSource" closed.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748434> <BEA-001128> <Connection for pool "DataSource" closed.>

i know this,
The cause of the problem is: owing to the client's operations staff to modify the datasource ,and reployed
thinks

Enhanced 3 fields unavailable in BI after DS enhancement

I did datasource enhancement in R/3 to add 3 fields into DS "0FI_GL_4". Then I go to RSA6 to click unhide for those 3 fields, activate DS. And then I put coding in CMOD. After that I replicate DS to BW system. I found those 3 fields are existing in DS, but the Transfer check box show uncheck for those 3 fields. That mean those 3 enhanced fields are still unavailable in BI. Does anybody know the reason for that?

Hi,
Need few clarifications.
You said that Transfer check box is Unchecked. Which Transfer check box you are refering to?
Regards,
Nagasekhar

How do I use a JNDI datasource in my application?

Not sure how to access the JNDI datasource i setup in my config.xml. I tried to browse it at rmi://localhost:1099/ but it only shows jmxrmi in the tree.
My config.xml looks like
<n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/server wlevs_server_config.xsd" xmlns:n1="http://www.bea.com/ns/wlevs/config/server" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<netio>
    <name>NetIO</name>
    <port>9002</port>
</netio>
<work-manager>
    <name>JettyWorkManager</name>
    <min-threads-constraint>5</min-threads-constraint>
    <max-threads-constraint>10</max-threads-constraint>
</work-manager>
<jetty>
    <name>JettyServer</name>
    <network-io-name>NetIO</network-io-name>
    <work-manager-name>JettyWorkManager</work-manager-name>
</jetty>
<rmi>
    <name>RMI</name>
    <http-service-name>JettyServer</http-service-name>
</rmi>
<jndi-context>
    <name>JNDI</name>
</jndi-context>
<exported-jndi-context>
    <name>exportedJndi</name>
    <rmi-service-name>RMI</rmi-service-name>
</exported-jndi-context>
<jmx>
    <jndi-service-name>JNDI</jndi-service-name>
    <rmi-service-name>RMI</rmi-service-name>
    <rmi-registry-port>1099</rmi-registry-port>
    <rmi-jrmp-port>9999</rmi-jrmp-port>
</jmx>
<transaction-manager>
      <name>transactionmanager</name>
      
</transaction-manager>
<data-source>
      <name>hqsqlconn</name>
      <driver-params>
        <url>jdbc:hsqldb:hsql://localhost/wlevdb</url>
        <driver-name>org.hsqldb.jdbcDriver</driver-name>
        <properties>
          <element>
            <name>user</name>
            <value>sa</value>
          </element>
          <element>
            <name>password</name>
            <value></value>
          </element>
        </properties>
        <use-xa-data-source-interface>true</use-xa-data-source-interface>
      </driver-params>
      <connection-pool-params>
        <initial-capacity>1</initial-capacity>
        <max-capacity>5</max-capacity>
        <test-table-name>test_table</test-table-name>
      </connection-pool-params>
      <data-source-params>
        <jndi-names>
          <element>hqsqlconn</element>
        </jndi-names>
        <global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
      </data-source-params>
</data-source>
</n1:config>

I see what you are saying.
The JNDI approach should work-we will try to reproduce this internally.
I would recommend leveraging the OSGi service registry, instead of using JNDI, however. The Event Server is a modular server based on OSGi, so one should use the OSGi service registry whenever possible instead of using the jndi registry. Jndi is primarily there to support legacy code that requires Jndi.
Any data sources that you configure are automatically registered in the OSGi service registry. When there is more than one data source they can be distinguished using their name.
There are a couple of options.
If you want to inject a reference to your datasource into a Spring bean, you can use an annotation, @Service, to annotate a setter method on your bean (see my previous post). The container will then inject a reference to the data source into the bean.
You can also put the following in your spring application context file
<osgi:reference id="myDataSource"
interface="javax.sql.DataSource"/>
This creates a bean proxy that references the datasource by looking up the datasource in the OSGi service registry. It works similarly to JndiObjectFactoryBean, but it uses the OSGi service registry instead of the JNDI registry. You can read more about it here
http://www.springframework.org/osgi/specification
(Look in section 3.3)
Hope that helps.
Seth
Edited by swhite at 08/01/2007 6:19 PM

Deploying EJB 3.0 entity beans without a Datasource

[Cross-posted from the TopLink list]
My question: Is there any way to configure the container or persistence provider to defer trying to connect to the Datasource until I make some call that involves persistence? Or any other way to deploy an app containing entity beans without having a database configured?
Background: I am working on a component that can be configured to run in either persistent or in-memory mode. For the persistent mode we would like to use EJB 3.0 entity beans; for the in-memory mode we would like the component to be deployable without having to have a database available.
However in my prototype of the application, when I try to deploy to OC4J 10.1.3, as soon as the entity beans are detected the TopLink persistence provider tries to establish a connection to the db via either the configured or default DataSource. So if the db is unavailable, deployment fails. Since this is occuring at deployment, it happens regardless of whether I am actually using any persistence features or not.

Hi,
I'm experiencing same problems, is this a bug or an feature?

How can we assign Extract Structure of datasource to request to transport

Hi,
I was trying to transport datasource. But it ended with errors due to unavailability of extract structure. So plz guide me how I can assign Extract structure of datasource to request to transpport.
I tried to assign in RSA6 but here there is no option to extract structure to assing to request.

Hi,
Normally when you get the screen to select and hide the fileds and then save it, you will get the extract structure collected automaticaly in your TP request.
Hope it helps
Regards,
Srini

Datasource pool are not recovered

Sometimes in our environment, weblogic lose the connection with the database for any reason:
- the network between weblogic server and data base server have some crash
- the data base is out
Most of the times, as soon as the connection is reestablished, the data source connections of the pool become available again. We have the properties 'test Frequency' and 'Test Table Name' setted.
But, in some cases not yet identified, the datasource pool keeps unavailable. The datasource isn't recovered even if it is restarted. The only solution is to restart weblogic server (version 10.3.2).
This happen in production and development environment. Unfortunately we couldn't map all variables that make this happen in order to reproduce it.
Does anybody have faced the same problem? Any hint?
Thanks. Mauro.

You could try setting the property Test Connections On Reserve on the connection pool. Now the connection will be tested
before it is given to the client.
Also the Test Frequency property can be used to test unused connections if they are still valid. By default this is set to 120
seconds.

JMSServer unavailable

Hi,
We are using WebLogic 8.1 SP6 in Solaris (Solaris 10 1/06 s10s_u1wos_19a SPARC). JDK 1.4_11.
We have a clustered environment using two physical servers, with two WebLogic servers per physical server, making a cluster composed by a total of four servers. Our application is deployed in this cluster.
The application has few JMSServers, being one of them the following:
<JMSServer Name="EGMSServer@ServerA1" Targets="ServerA1">
<JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
ExpirationPolicy="Log"
JNDIName="jms/Queue1ServerA1"
Name="Queue1@ServerA1"
RedeliveryDelayOverride="10000" RedeliveryLimit="1" StoreEnabled="default"/>
<JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
ExpirationPolicy="Log"
JNDIName="jms/Queue2ServerA1"
Name="Queue2@ServerA1"
RedeliveryDelayOverride="0" RedeliveryLimit="0" StoreEnabled="default"/>
<JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
ExpirationPolicy="Log"
JNDIName="Queue3ServerA1"
Name="Queue3@ServerA1"
RedeliveryDelayOverride="10000" RedeliveryLimit="1" StoreEnabled="default"/>
<JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
ExpirationPolicy="Log"
JNDIName="Queue4ServerA1"
Name="Queue4@ServerA1"
RedeliveryDelayOverride="10000" RedeliveryLimit="1" StoreEnabled="default"/>
</JMSServer>
Obviously the definition of this JMSServer is repeated for each member of the cluster.
All worked fine until yesterday at night. We had a big volume of workload and our transactions started to fail due the following reason:
2007-08-31 05:04:14,775;[ExecuteThread: '4' for queue: 'activity'];trg.TrgService;ERROR;weblogic.jms.common.JMSException: Internal error: XAResource 'JMS_EGJMSServer@ServerA2_NotDurable' is unavailable
2007-08-31 05:04:14,784;[ExecuteThread: '4' for queue: 'activity'];util.DBService;ERROR;java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: delist() failed on resource 'JMS_EGJMSServer@ServerA2_NotDurable'.
Internal error: XAResource 'JMS_EGJMSServer@ServerA2_NotDurable' is unavailable
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1604)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1512)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:455)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:410)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:344)
     at DatabaseConnectionPool.getConnection(DatabaseConnectionPool.java:28)
     at Module.getInboundConnection(Module.java:130)
     at DBService.updateIpDataTransmLog(DBService.java:1008)
     at Service.process(bService.java:269)
     at activity.postprocessor.InPostProcessor.processImpl(InPostProcessor.java:88)
     at StageAbs.timebox(StageAbs.java:80)
     at StageAbs.process(StageAbs.java:46)
     at core.bridge.MDBBridgeDelegate.onMessage(MDBBridgeDelegate.java:55)
     at activity.bridge.impl.ejb.EventQueueMDB.onMessage(EventQueueMDB.java:73)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
We observed that few minutes before this problem the JMSServer EGJMSServer became unavailable in the server where the crash took place, and stayed unavailable for 5 minutes. It seems that this unavailability caused this failure. I am including the relevant server logs:
####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-110030> <XA resource [JMS_EGJMSServer@ServerA2_NotDurable] has not responded in the last 0 second(s).>
####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '1' for queue: 'activity'> <<anonymous>> <BEA1-288E8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '2' for queue: 'activity'> <<anonymous>> <BEA1-288C8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '3' for queue: 'ctivity'> <<anonymous>> <BEA1-288F8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '4' for queue: 'activity'> <<anonymous>> <BEA1-288D8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
####<Aug 31, 2007 5:02:26 AM MEST> <Info> <EJB> <barge> <ServerA2> <ExecuteThread: '0' for queue: 'activity'> <<anonymous>> <> <BEA-010213> <Message-Driven EJB: DbSpoolEventQueueMDB's transaction was rolledback. The transaction details are: Xid=BEA1-28908324BAE684A42059(20710803),Status=Rolled back. [Reason=javax.jms.JMSException: failed to enlist the transaction],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,SCInfo[xxx+ServerA2]=(state=rolledback),local properties=({weblogic.jdbc.jta.IntegXAConnectionPool=weblogic.jdbc.wrapper.TxInfo@15eb303}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ServerA2+barge:7032+xxx+t3+, XAResources={JMS_EGJMSServer@ServerA2_NotDurable, JMS_ZZZJMSServer@ServerA2_NotDurable, Sys2ConnectionPool, Sys1ConnectionPool, IntegXAConnectionPool},NonXAResources={})],CoordinatorURL=ServerA2+barge:7032+xxx+t3+).>
(2.1) ####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '2' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288C8324BAE684A42059(33313611),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable - with nested exception:
[javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1687)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
.>
####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '3' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288F8324BAE684A42059(21874355),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(ServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(state=started,assigned=none),xar=JMS_EGJMSServer@ServerA2_NotDurable,re-Registered = false),XAServerResourceInfo[IntegXAConnectionPool]=(ServerResourceInfo[IntegXAConnectionPool]=(state=rolledback,assigned=ServerA2),xar=IntegXAConnectionPool,re-Registered =
####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '1' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288E8324BAE684A42059(30340443),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(ServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(state=started,assigned=none),xar=JMS_EGJMSServer@ServerA2_NotDurable,re-Registered = false),XAServerResourceInfo[IntegXAConnectionPool]=(ServerResourceInfo[IntegXAConnectionPool]=(state=rolledback,assigned=ServerA2),xar=IntegXAConnectionPool,re-Registered
####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '4' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288D8324BAE684A42059(5134189),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(ServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(state=started,assigned=none),xar=JMS_EGJMSServer@ServerA2_NotDurable,re-Registered = false),XAServerResourceInfo[IntegXAConnectionPool]=(ServerResourceInfo[IntegXAConnectionPool]=(state=rolledback,assigned=ServerA2),xar=IntegXAConnectionPool,re-Registered =
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
.>
We have never had this problem and we are clueless about what could have caused it. It was during a moment of a workload pick.
Could you please advice us on what could be causing this JMSServer to became unavailable? What can justify this problem and wow can we preventit?
Many thanks!

Same here. I cannot register for skype manager, it fails on login with the usual:
"Oops, something went wrong...
We're having technical problems. We're sorry for the inconvenience. Please try again after a few minutes.
Thank you."
Skype heartbeat says everything is ok. Please can we get an update on this?

XA Datasource specified, visible in server, not working...

I'm working with Glassfish, Toplink, and Postgres.
I have a session bean that injects a persistence context and another session bean that also has a persistence context. ie:
@Stateless
public class AccountManagerEJBBean
        extends    SomeBaseClass
        implements SomeApplication.model.AccountManagerEJB
    @PersistenceContext
    private EntityManager _manager;
    @EJB
    private ConfigEJB configEJB;
    //The above bean also has a persistence context member.
//...etcWhen I call _manager.persist() , I get the following exception :
java.lang.IllegalStateException: Local transaction already has 1 non-XA Resource: cannot add more resources.The datasource that this bean is using is configured as an XA datasource. In the Admin Console, under Resources > JDBC > Connection Pools > [myConnectionPool] , the Resouce Type is "javax.sql.XADataSource".
This reflects the configuration specified in my sun-resources.xml
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.postgresql.ds.PGSimpleDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jdbc/SomeConnectionPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.XADataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">I don't know if this should matter, but the injected EJB (ConfigEJB) is from another module, within the same application, that uses the same datasource.
Does anybody know what I am missing? Any help would be really appreciated.

Update:
I was unable to recover the system and had to reinstall everything from scratch.
I still have massive problems using my wildcard SSL certificate.
When connecting to my https-port I get an unavailable error with SSL installed/active.
When I set it up without SSL-certificate and connect to the same port its is active with an unsigned certificate.
Anyone knows what the problem is?

Portlet unavailable

I'm working on the WebCenter Framework Tutorial. I was able to deploy and run my portlet in Step # 6. In Step # 7 (Adding Some Simple Logic ot the Portlet) I now get a "Portlet Unavailable" error when I try to run my portlet. I checked to verify that OC4J is running by going to the Connections Navigator tab->MyLocalOC4J and selected properties. From the test tab I checked the test button and had a successful connection.
When I right click on the MyPage.jspx and click run it gives me the "Portlet unavialable" error message in the page that it opens up. Here is the rest of the error message. If you can help I would greatly appreciate it.
Thanks...
C:\Oracle\JDeveloper\jdk\bin\javaw.exe -jar C:\Oracle\JDeveloper\j2ee\home\admin.jar ormi://10.10.112.73:23891 oc4jadmin **** -updateConfig
Sep 30, 2008 3:24:35 PM com.evermind.server.XMLDataSourcesConfig parseRootNode
INFO: Legacy datasource detected...attempting to convert to new syntax.
Sep 30, 2008 3:24:40 PM com.oracle.corba.ee.impl.orb.ORBServerExtensionProviderImpl preInitApplicationServer
WARNING: ORB ignoring configuration changes. Restart OC4J to apply new ORB configuration.
Ready message received from Oc4jNotifier.
Embedded OC4J startup time: 9016 ms.
Target URL -- http://10.10.112.73:8988/MySample-ViewController-context-root/faces/MyPage.jspx
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.Short,null)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(null,java.lang.Short)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.Byte,null)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(null,java.lang.Byte)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.Integer,null)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(null,java.lang.Integer)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.Long,null)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(null,java.lang.Long)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.Float,null)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(null,java.lang.Float)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.Double,null)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(null,java.lang.Double)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ValidatorRule end
WARNING: [ValidatorRule]{faces-config/validator} Merge(javax.faces.LongRange)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.DateTime,null)
Sep 30, 2008 3:24:48 PM com.sun.faces.config.rules.ConverterRule end
WARNING: [ConverterRule]{faces-config/converter} Merge(javax.faces.Number,null)
Sep 30, 2008 3:24:48 PM oracle.adf.share.config.ADFConfigFactory findOrCreateADFConfig
INFO: oracle.adf.share.config.ADFConfigFactory Reading META-INF/adf-config.xml
08/09/30 15:24:49 PortletContainer portletTechnologies set to '{oracle.portlet.client.containerimpl.web.WebPortletTechnologyConfig,oracle.portlet.client.containerimpl.wsrp.WSRPPortletTechnologyConfig}' from adf-config.xml
08/09/30 15:24:49 PortletContainer defaultTimeout set to '20' from adf-config.xml
08/09/30 15:24:49 PortletContainer minimumTimeout set to '1' from adf-config.xml
08/09/30 15:24:49 PortletContainer maximumTimeout set to '60' from adf-config.xml
08/09/30 15:24:49 PortletContainer resourceProxyPath set to '/resourceproxy' from adf-config.xml
Sep 30, 2008 3:24:50 PM oracle.adfinternal.view.faces.application.ViewHandlerImpl _checkTimestamp
INFO: ADF Faces is running with time-stamp checking enabled. This should not be used in a production environment. See the oracle.adf.view.faces.CHECK_FILE_MODIFICATION property in WEB-INF/web.xml
Sep 30, 2008 3:24:50 PM oracle.portlet.client.utils.PortletLogger info
INFO: Portlet Client MBeans registered
Sep 30, 2008 3:24:50 PM oracle.jsp.logger.JspMessages infoProviderURIUsed
INFO: Using the ProviderURI /mdssys/ViewController/public_html/MyPage.jspx that is returned from custom provider for processing requests.
08/09/30 15:24:51 DefaultValidationEventHandler: [ERROR]: ClassLoader "current-workspace-app.web.MySample-ViewController-webapp:0.0.0" (from <web-module> in /C:/Oracle/jdevinstance10132/mywork/MySample/ViewController/public_html/): This loader has been closed and should not be in use.
Location: obj: oracle.portlet.wsrp.v2.impl.MarkupParamsImpl@782c68
Sep 30, 2008 3:24:54 PM oracle.adfinternal.view.faces.renderkit.html.portlet.PortletRenderer preRender
SEVERE: oracle.adf.model.portlet.binding.PortletBindingException: Error converting the following bean from JAXB package 'oracle.portlet.wsrp.v2' to SOAP:
oracle.portlet.wsrp.v2.impl.GetMarkupElementImpl {0}
[PortletContext] oracle.portlet.wsrp.v2.impl.PortletContextImpl {1}
[PortletState] array {2}
[Extensions] array {3}
[ScheduledDestruction] <null>
[ExtensionsLength] 0
[PortletHandle] "E:0:10.10.112.73:-188af61e:11caecec4b7:-7ffd"
[MarkupParams] oracle.portlet.wsrp.v2.impl.MarkupParamsImpl {4}
[MarkupCharacterSets] array {5}
[0] "UTF-8"
[Extensions] array {6}
[MimeTypesLength] 4
[NavigationalState] ""
[ExtensionsLength] 0
[ValidNewModesLength] 7
[WindowState] "wsrp:normal"
[MimeTypes] array {7}
[0] "text/html"
[1] "text/xml"
[2] "text/vnd.oracle.mobilexml"
[3] "*"
[ecureClientCommunication] false
[Locales] array {8}
[0] "en-US"
[NavigationParameters] array {9}
[ClientData] oracle.portlet.wsrp.v2.impl.ClientDataImpl {10}
[ExtensionsLength] 0
[Extensions] array {11}
[UserAgent] "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)"
[CcppHeaders] <null>
[Mode] "wsrp:view"
[NavigationParametersLength] 0
[MarkupCharacterSetsLength] 1
[ValidateTag] <null>
[ValidNewWindowStates] array {12}
[0] "wsrp:normal"
[1] "wsrp:maximized"
[2] "wsrp:minimized"
[LocalesLength] 1
[ValidNewWindowStatesLength] 3
[ValidNewModes] array {13}
[0] "wsrp:view"
[1] "urn:javax:portlet:mode:custom:edit_defaults"
[2] "wsrp:edit"
[3] "wsrp:help"
[4] "urn:javax:portlet:mode:custom:about"
[5] "urn:javax:portlet:mode:custom:print"
[6] "urn:javax:portlet:mode:custom:config"
[UserContext] oracle.portlet.wsrp.v2.impl.UserContextImpl {14}
[UserCategories] array {15}
[ExtensionsLength] 0
[UserContextKey] "PUBLIC"
[Profile] <null>
[UserCategoriesLength] 0
[Extensions] array {16}
[RuntimeContext] oracle.portlet.wsrp.v2.impl.RuntimeContextImpl {17}
[UserAuthentication] "wsrp:none"
[TransientPropertiesLength] 0
[NamespacePrefix] "__ns1960239081_"
[SessionID] <null>
[Extensions] array {18}
[ExtensionsLength] 0
[Templates] <null>
[TransientProperties] array {19}
[PortletInstanceKey] "1960239081"
[RegistrationContext] oracle.portlet.wsrp.v2.impl.RegistrationContextImpl {20}
[ExtensionsLength] 0
[RegistrationHandle] "C:10.10.112.73:-188af61e:11caecec4b7:-7ffe"
[Extensions] array {21}
[RegistrationState] array {22}
[ScheduledDestruction] <null>
     at oracle.adf.model.portlet.binding.PortletBinding.getPortletRendition(PortletBinding.java:522)
     at oracle.adfinternal.view.faces.renderkit.html.portlet.PortletRenderer.preRender(PortletRenderer.java:417)
     at oracle.adfinternal.view.faces.renderkit.html.customizable.ShowDetailFrameRenderer.encodeBegin(ShowDetailFrameRenderer.java:227)
     at oracle.adf.view.faces.component.UIXComponentBase.encodeBegin(UIXComponentBase.java:593)
     at oracle.adfinternal.view.faces.renderkit.RenderUtils.encodeRecursive(RenderUtils.java:39)
     at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeChild(CoreRenderer.java:242)
     at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeAllChildren(CoreRenderer.java:265)
     at oracle.adfinternal.view.faces.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:65)
     at oracle.adfinternal.view.faces.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:117)
     at oracle.adfinternal.view.faces.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:147)
     at oracle.adfinternal.view.faces.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:60)
     at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeEnd(CoreRenderer.java:169)
     at oracle.adf.view.faces.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:624)
     at javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:645)
     at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:568)
     at oracle.adf.view.faces.webapp.UIXComponentTag.doEndTag(UIXComponentTag.java:100)
     at mdssys.viewcontroller._public__html._MyPage_jspx._jspService(_MyPage_jspx.java:102)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
     at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:724)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:414)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:598)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:522)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.mds.jsp.MDSJSPFilter.doFilter(Unknown Source)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:622)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
     at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:286)
     at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:50)
     at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:192)
     at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:197)
     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:346)
     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:152)
     at oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:157)
     at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:137)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:214)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:228)
     at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:197)
     at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:123)
     at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:103)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:162)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:620)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:215)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: Error converting the following bean from JAXB package 'oracle.portlet.wsrp.v2' to SOAP:
oracle.portlet.wsrp.v2.impl.GetMarkupElementImpl {0}
[PortletContext] oracle.portlet.wsrp.v2.impl.PortletContextImpl {1}
[PortletState] array {2}
[Extensions] array {3}
[ScheduledDestruction] <null>
[ExtensionsLength] 0
[PortletHandle] "E:0:10.10.112.73:-188af61e:11caecec4b7:-7ffd"
[MarkupParams] oracle.portlet.wsrp.v2.impl.MarkupParamsImpl {4}
[MarkupCharacterSets] array {5}
[0] "UTF-8"
[Extensions] array {6}
[MimeTypesLength] 4
[NavigationalState] ""
[ExtensionsLength] 0
[ValidNewModesLength] 7
[WindowState] "wsrp:normal"
[MimeTypes] array {7}
[0] "text/html"
[1] "text/xml"
[2] "text/vnd.oracle.mobilexml"
[3] "*"
[ecureClientCommunication] false
[Locales] array {8}
[0] "en-US"
[NavigationParameters] array {9}
[ClientData] oracle.portlet.wsrp.v2.impl.ClientDataImpl {10}
[ExtensionsLength] 0
[Extensions] array {11}
[UserAgent] "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)"
[CcppHeaders] <null>
[Mode] "wsrp:view"
[NavigationParametersLength] 0
[MarkupCharacterSetsLength] 1
[ValidateTag] <null>
[ValidNewWindowStates] array {12}
[0] "wsrp:normal"
[1] "wsrp:maximized"
[2] "wsrp:minimized"
[LocalesLength] 1
[ValidNewWindowStatesLength] 3
[ValidNewModes] array {13}
[0] "wsrp:view"
[1] "urn:javax:portlet:mode:custom:edit_defaults"
[2] "wsrp:edit"
[3] "wsrp:help"
[4] "urn:javax:portlet:mode:custom:about"
[5] "urn:javax:portlet:mode:custom:print"
[6] "urn:javax:portlet:mode:custom:config"
[UserContext] oracle.portlet.wsrp.v2.impl.UserContextImpl {14}
[UserCategories] array {15}
[ExtensionsLength] 0
[UserContextKey] "PUBLIC"
[Profile] <null>
[UserCategoriesLength] 0
[Extensions] array {16}
[RuntimeContext] oracle.portlet.wsrp.v2.impl.RuntimeContextImpl {17}
[UserAuthentication] "wsrp:none"
[TransientPropertiesLength] 0
[NamespacePrefix] "__ns1960239081_"
[SessionID] <null>
[Extensions] array {18}
[ExtensionsLength] 0
[Templates] <null>
[TransientProperties] array {19}
[PortletInstanceKey] "1960239081"
[RegistrationContext] oracle.portlet.wsrp.v2.impl.RegistrationContextImpl {20}
[ExtensionsLength] 0
[RegistrationHandle] "C:10.10.112.73:-188af61e:11caecec4b7:-7ffe"
[Extensions] array {21}
[RegistrationState] array {22}
[ScheduledDestruction] <null>
     at oracle.portlet.utils.SoapJaxbTranslationUtils.jaxbToSoap(SoapJaxbTranslationUtils.java:154)
     at oracle.portlet.wsrp.v2.WSRP_v2_Markup_PortTypeJaxbToSoap.toSoap(WSRP_v2_Markup_PortTypeJaxbToSoap.java:42)
     at oracle.portlet.wsrp.v2.WSRP_v2_Markup_PortTypeJaxbToSoap.getMarkup(WSRP_v2_Markup_PortTypeJaxbToSoap.java:79)
     at oracle.portlet.wsrp.v2.ServerToWSRPv2.getMarkup(ServerToWSRPv2.java:13461)
     at oracle.portlet.client.connection.wsrp.ActivityServerWrapper.getMarkup(ActivityServerWrapper.java:1330)
     at oracle.portlet.client.techimpl.wsrp.WSRPGetMarkupPipe.execute(WSRPGetMarkupPipe.java:116)
     at oracle.portlet.client.techimpl.wsrp.WSRPGetMarkupPipe.pre(WSRPGetMarkupPipe.java:52)
     at oracle.portlet.client.service.pipeline.PipeContext.internalExecute2(PipeContext.java:516)
     at oracle.portlet.client.service.pipeline.PipeContext.internalExecute(PipeContext.java:403)
     at oracle.portlet.client.service.pipeline.PipeContextRunnable.run(PipeContextRunnable.java:24)
     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:431)
     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
     at oracle.portlet.client.service.pipeline.ModifiedThreadPoolExecutor$Worker.runTask(ModifiedThreadPoolExecutor.java:398)
     at oracle.portlet.client.service.pipeline.ModifiedThreadPoolExecutor$Worker.run(ModifiedThreadPoolExecutor.java:423)
     ... 1 more
Caused by: javax.xml.bind.MarshalException
- with linked exception:
[com.sun.xml.bind.serializer.AbortSerializationException: ClassLoader "current-workspace-app.web.MySample-ViewController-webapp:0.0.0" (from <web-module> in /C:/Oracle/jdevinstance10132/mywork/MySample/ViewController/public_html/): This loader has been closed and should not be in use.]
     at oracle.portlet.wsrp.v2.impl.runtime.MarshallerImpl.write(MarshallerImpl.java:166)
     at oracle.portlet.wsrp.v2.impl.runtime.MarshallerImpl.marshal(MarshallerImpl.java:101)
     at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:87)
     at oracle.portlet.utils.SoapJaxbTranslationUtils.jaxbToSoap(SoapJaxbTranslationUtils.java:114)
     ... 14 more

Hi,
The error messages seems to indicate that there is some kind of mismatch between the consumer and the provider regarding the soap messages. This can sometimes happen when the specs of the portlet change: adding of portlet communication parameters in the oracle-portlet.xml for example, or registering of security roles. Here are some steps:
- restart the webcenter container
- stop the embedded OC4J
- refresh the portlet registration in the consumer project
- check if the portlet on the page is still having correct bindings, or delete the portlet from the page and put it on again
- retry.
- if any errors are left, also check the application.log of the deployed portlet project for any detail errors. Portlet-application specific error messages do not always appear in the container logging, but can end up in the application log file.
Success,
Jeroen van Veldhuizen

DataSource unavailable

Similar Messages

Maybe you are looking for