Javax.jms.InvalidSelectorException occurs when upgrade to weblogic 12c

Question

Recently, our team upgrade weblogic server from 11g to 12c,  some errors occur when start web application in weblogic domain.
The error is related to message driven bean,  below is the part of  ejb-jar.xml definition:
  <message-driven id="message-driven_1">
      <description>Message Driven Bean</description>
      <display-name>Message Configuration (MDB)</display-name>
      <ejb-name>Logger</ejb-name>
      <ejb-class>com.logging.mdb.Logger</ejb-class>
      <messaging-type>javax.jms.MessageListener</messaging-type>
      <transaction-type>Container</transaction-type>
      <message-destination-type>javax.jms.Queue</message-destination-type>
      <activation-config>
            <activation-config-property>
                <activation-config-property-name>messageSelector</activation-config-property-name>
                <activation-config-property-value>DELIVERY='IMMEDIATE'</activation-config-property-value>
            </activation-config-property>
            <activation-config-property>
                <activation-config-property-name>acknowledgeMode</activation-config-property-name>
                <activation-config-property-value>Auto-acknowledge</activation-config-property-value>
            </activation-config-property>
            <activation-config-property>
                 <activation-config-property-name>destinationType</activation-config-property-name>
                 <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
            </activation-config-property>
      </activation-config>
  </message-driven>
When start application below errors show up:
<Dec 18, 2013 6:24:05 AM PST> <Warning> <EJB> <SLC02PGO> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1387376645415> <BEA-010061> <The Message-Driven EJB Logger is unable to connect to the JMS destination edx/queue/logger. The Error was:
javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
####<Dec 18, 2013 6:24:15 AM PST> <Warning> <EJB> <SLC02PGO> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1387376655414> <BEA-010096> <The Message-Driven EJB MessageDispatcher is unable to connect to the JMS destination or bind to JCA resource adapter edx.queue.outbound. The onnection failed after 124 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
It works well in weblogic 11g,   not sure whether there's any changes in weblgic 12c.
I'm appreciate if there's someone can help me on this issue.
    <message-driven id="message-driven_1">
      <description>Message Driven Bean</description>
      <display-name>Message Configuration (MDB)</display-name>
      <ejb-name>Logger</ejb-name>
      <ejb-class>com.edocs.fs.logging.mdb.Logger</ejb-class>
      <messaging-type>javax.jms.MessageListener</messaging-type>
      <transaction-type>Container</transaction-type>
      <message-destination-type>javax.jms.Queue</message-destination-type>
      <activation-config>
        <activation-config-property>
          <activation-config-property-name>messageSelector</activation-config-property-name>
          <activation-config-property-value>DELIVERY='IMMEDIATE'</activation-config-property-value>
        </activation-config-property>
        <activation-config-property>
          <activation-config-property-name>acknowledgeMode</activation-config-property-name>
          <activation-config-property-value>Auto-acknowledge</activation-config-property-value>
        </activation-config-property>
        <activation-config-property>
          <activation-config-property-name>destinationType</activation-config-property-name>
          <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
        </activation-config-property>
      </activation-config>
      <resource-ref id="ResRef_Logger_1">
        <res-ref-name>jdbc/LoggerDataSource</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
      </resource-ref>
    </message-driven>

Answer 1

Hi,
I debug the application, I found my @ViewScoped ManagedBeans, they're recreated after you click a button or select a item in combobox
Here is a piece of code:
    @PostConstruct
    public void resolveEntity() {
        Object sEntity = FacesContext.getCurrentInstance().getExternalContext().getSessionMap().get("entity");
        entity = (BctTbOportunidade) sEntity;
         FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove("entity");
        if (entity == null) {
            entity = new BctTbOportunidade();
I use @postConstruct to get a entity from another page in sessionMap(I set a item from a table and use this method to modify a entity in a other page).
When I click a button or select a item in combobox in same page @PostConstruct method is called but values are lost. No Exceptions are thrown by server.
I found a artice written by BalluC that some versions of jsf 2.1 has this behavior The BalusC Code: The benefits and pitfalls of @ViewScoped
I already configured my web.xml to set false javax.faces.PARTIAL_STATE_SAVING 
But this behavior continues.
The jsf version deployed in my weblogic 12c is 2.1.7.