Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
[WLI-Core:489049]Could not determine channel type
via Oracle Community by 3004, 2 years ago
[WLI-Core:489049]Could not determine channel type
via Oracle Community by 666705, 2 years ago
[WLI-Core:489049]Could not determine channel type
via hivmr.com by Unknown author, 2 years ago
[WLI-Core:489049]Could not determine channel type
com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: [WLI-Core:489049]Couldnot determine channel type at com.bea.wli.mbconnector.jms.JmsConnMDB.publishMBMessage(JmsConnMDB.java:276) at com.bea.wli.mbconnector.jms.JmsConnMDB.onMessage(JmsConnMDB.java:466) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382) at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)