Sender JMS Connectivity not working

Hi All,
We have developed a scenario where we have to pick messages from DTS JMS queue and we are using JMS provider with JNDI as the sender transport protocol. We have deployed the jar files given by the DTS team successfully in our XI 3.0 system and we have configured the sender JMS channel. Since this queue is in another NWDS sever, we have also set Additional JMS parameters: JNDI.InitialContext.property.5=java.lang.String force_remote, java.lang.String true.
But when we are testing, I am getting the below error in Adapter monitoring :
Sender channel. Details: com/sap/jms/client/connection/RemoteConnectionFactoryInterface (Unsupported major.minor version 49.0)
Please let me know if I have missed any parameters or any suggestions to solve the issue.
Thanks,
Laawanya

Hello Stefan - Thanks for response.
Here are the Parameters.......
Adapter Type: JMS
Sender Type Clicked
Transport protocol:WebSphereMQ (non-JMS)
Message protocol:JMS 1.x
Adapter Engine:Integration Server
Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class:com.ibm.mq.jms.MQQueue
IP Address or Server Name:10.9.48.154
Server Port:1414
Queue Manager Name:WBIDEV
Channel Name:WBI.XI.SVRCONN
JMS Queue:XI_REQUEST
Transport/Network Protocol:TCP/IP
JMS-Compliant:JMS-Compliant
Transactional JMS Session:Check box Set
JMS Queue User:XIUSER
JMS Queue Password:********
Set XI message ID(MessageID) to:GUID(recommended value)
Set XI cenversation ID(conversationID) to:No value
Mapping of Message:Message Payload=JMS Payload
Quality of Service:Exactly Once
Time Period for duplicate check for EO(IO)(secs):86400
Wait After Message Error(msecs):1000
Wait before Reconnect(msecs):1000
Status:Active
The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
Pls advice If I am missing anything ?
Thanks....
Amrish.

Similar Messages

Sender JMS Adapter - NOT Working

Hello Everybody - We are on SP13, also installed JMS Driver files on the system. We are running, Central Adapter Engine.
We configured the Sender JMS Adapter for WBI MQ->XI->SAP scenario. We need to JMS Adapter to be configured to connect to WBI from XI. Everything looks great in configuration but in the Adpater Monitoring, JMS Adapter is with Error Status and Message says "Sender channel. Details: (No detail information set.)".
Does anybody has any idea about this error ?
I checked SAP Help link as well on this. Based on this link http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm. Do we need to configure this JMS Adapter somewhere on teh server as well ? If yes, then where ? Pls respond if you have any clue about it.
Thanks in anticipation...

Hello Stefan - Thanks for response.
Here are the Parameters.......
Adapter Type: JMS
Sender Type Clicked
Transport protocol:WebSphereMQ (non-JMS)
Message protocol:JMS 1.x
Adapter Engine:Integration Server
Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class:com.ibm.mq.jms.MQQueue
IP Address or Server Name:10.9.48.154
Server Port:1414
Queue Manager Name:WBIDEV
Channel Name:WBI.XI.SVRCONN
JMS Queue:XI_REQUEST
Transport/Network Protocol:TCP/IP
JMS-Compliant:JMS-Compliant
Transactional JMS Session:Check box Set
JMS Queue User:XIUSER
JMS Queue Password:********
Set XI message ID(MessageID) to:GUID(recommended value)
Set XI cenversation ID(conversationID) to:No value
Mapping of Message:Message Payload=JMS Payload
Quality of Service:Exactly Once
Time Period for duplicate check for EO(IO)(secs):86400
Wait After Message Error(msecs):1000
Wait before Reconnect(msecs):1000
Status:Active
The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
Pls advice If I am missing anything ?
Thanks....
Amrish.

Jms is not working properly in clustered environment

Hi all,
i am using the application server oc4j 10.1.3.1.0 enterprise edition . my application is standalone application(thick client)
we are using the jndi.properties as follows ...
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
java.naming.provider.url=opmn:ormi://172.16.1.38:6005:group/Security,opmn:ormi://172.16.1.38:6006:deceval_group/Security
java.naming.security.principal=oc4juser
java.naming.security.credentials=oc4juser
oracle.j2ee.rmi.loadBalance=lookup
we have two application servers in cluster topology as u can see above we have used one instance from one application server and one from another.
i have seen that for every instance there one jms server. at runtime it is taking one application servers services
say opmn port 6005 but when the application is connecting to the another application server say opmn 6006
here jms is not working properly when i send message
As we have clustered environment message must be propagated all the applications who use above jndi.properties.
if i keep use only one application server opmn say
java.naming.provider.url=opmn:ormi://172.16.1.38:6005:group/Security
then its is working excellently
please can u provide any solution ASAP
thanks in advance
Manu

Dear Aravindth
(.*?) means -> Select all contents from where you start and end,
For Ex. <month>(.*?)</month> then Select for start <month> and end last </month> tag.
(?) Match zero or one occurrences. Equivalent to {0,1}.
(*) Match zero or more occurrences. Equivalent to {0,}.
(+) Match one or more occurrences. Equivalent to {1,}.
(.) (Dot). Match any character except newline or another Unicode line terminator.
(.*?) means -> Zero or more times Match any character except newline or another Unicode line terminator + Match zero or more occurrences. Equivalent to {0,}.+Match zero or one occurrences. Equivalent to {0,1}.
Could you please refere the below cite :
http://www.javascriptkit.com/jsref/regexp.shtml
Thanks & Regards
T.R.Harihara SudhaN

HT201320 I have IOS 7 5S and using mail. Receiving works great. Sending mail will not work. Using Centurylink. On my IOS 6 Iphone 4 it works great. Compared settings and they are identical. Now what?

I have IOS 7 5S and using mail. Receiving works great. Sending mail will not work. Using Centurylink. On my IOS 6 Iphone 4 it works great. Compared settings and they are identical. Now what?

Well, this is a recurring issue for many users...a small percentage of users but still a bug. Report the issue here to Apple: www.apple.com/feedback
iOS7.0.3 will be released next week, which as of now, I know is primarily for an iMessage but hopefully it will clear up some of these email issues some are also having.

Send & Recieve functionality not working with WebDav after installing Acrobat XI

Send & Recieve functionality not working with WebDav after installing Acrobat XI for PDF. Acrobat XI is complete installations(Trial Version).

Hi Kiro ,
Did you try opening that file in any other browser ?If not ,please try doing that once and see if that works for you.
Try Repairing Acrobat once and see if that helps.
Launch Acrobat>Navigate to Help>Repair Acrobat Installation.
Regards
Sukrit Dhingra

Camera connection not working with my camera

Camera connect not working with my Sony boggie camera

The Bloggie will not work because it draws too much power from the USB port on the iPad. The solution is to interpose a powered USB hub between the Bloggie and the iPad - connect the Bloggie to the powered hub, then connect the hub to the ipad accessory. Works fine with my 3D Bloggie.

Send to is not working when a document library is associated with work flow.

Send to is not working when a document library is associated with work flow.
question is when a workflow is tied to list send to don't work ?
we get a ntlm login prompt sphoradically, if we cancel the prompt we and reload the page we get the resultsen

could you please give more detail about the issue?
What kind of the workflow associated to the Library and what error you getting when trying to perform send to?
check ULS logs...
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Send E-mail not working???

I'm having issues with the "send email" button not working. When I test (F4) the functionality of a quiz inside captivate 5 & 5.5 and get to the end of the quiz I click the send email button and it opens my email with the results in the body of the email like its supposed to...but when I publish the course launch the published html file and then take the quiz when I click the send email button nothing happens (literally nothing). Am I missing something simple? I don't remember this being an issue in previous version...
Thanks for the help
B

Hi there
Please investigate the link below
Click here to view
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

HT4865 my message send tab is not working, any idea why please, thanks in advance,

My message tab to send is not working,I can type the message but when I press send it 's not working,
I don't remember doing anything to stop it, Can anyone advise me please, thanks you in advance,

If you have Settings>Messages>Show Subject Field set to On, you may be typing in the subject field of your message. The Send button won't respond until you type something in the iMessage field just below it.

TS4268 My iMessage send button is not working. How do I get it to work?

My iMessage send button is not working. How do I get it to work?

Hi,
You may have a virus on your PC. Review this NBC Nightly news article.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

" send link" is not working , when click on it, nothing happens, but Firefox 4.0 will work

File --> Send link will not work after Update Firefox 4.0 to 8.0
It is happening all the time.
Before update, the 4.0 version will work.

File --> Send link will not work after Update Firefox 4.0 to 8.0
It is happening all the time.
Before update, the 4.0 version will work.

X-Fi Titanium PCI Express front pannel connection not working

<font face="verdana,geneva" size="3">I can not get any signal to or from the front pannel connector of my X-Fi Titanium PCI Express. (The rear jacks are working fine.)
<font face="verdana,geneva" size="3">The front header cable from my Antec P-80B worked perfectly with my onboard motherboard sound. Now that I have it connected to my X-Fi I get nothing from the jacks on the front of my case. (The onboard sound is disabled in my BIOS.)? I've double and tripple checked the connection and it is properly keyed and fitted. Is there a step or a setting that I'm missing somewhere to get this working? Can anyone confirm that the front pannel connection is acti've on the X-Fi Titanium PCI Express?

Re: X-Fi Titanium PCI Express front pannel connection not working? I was truly hoping that would help and I wanted to give you some additional hope. I have a coolermaster case, and it has the AC97 jack on the inside with all my other other front panel connectors for hard dri've activity light, reset, and power on. Three inches down from the AC97 jack, the INTEL HD *which works beautifully with the X-FI, only differs by three wires in different locations and the two pinouts configurations match those of the INTEL site identically.
Please tell me what happens as I would like to post a step by step guide for the others here in the forum. You will know when you have successfully adapted the connector because in VISTA and Windows 7, your sound applet in control panel will have a display of the connectors "lit up" when they are successfully connected. Mine shows FP microphone in the applet when its plugged in, and grayed out when its not. Its great for telling if I am connected on the rear of the soundcard of the front.
Best of luck and .......
Message Edited by jmacguire on 07-06-2009 :09 PM

Corporate connectivity not working for some users

Hi,
I'm having an issue that started about a month ago but is getting worse. A select group of users are no longer able to connect using DirectAccess, even though these users have been using their computers for a few months without issue.
BACKGROUND:
-Windows 2008 R2 DirectAccess server
-Windows 7 x64 enterprise clients
-Most clients experiencing the issue have a newer laptop (Lenovo T440 with Intel 7260AC wireless), but the issue is not limited to this model. Also, I have 25+ other Lenovo T440 units that connect without issue to this day.
TROUBLESHOOTING STEPS:
I have tried disabling the various interfaces used for directaccess on these problem machines and have not been able to narrow it down. Essentially- I've noticed the IP-HTTPS interface shows deactivated, so I'll disable Teredo. This
usually allows the IP-HTTPS to show activated, and connectivity is restored. However, after 30 seconds to a few minutes, connectivity will once again drop. So I'll re-enable teredo (default,client, or enterprise client) and connectivity will kick
on for another brief period, but drops again shortly after.
I have confirmed that during these short periods of connectivity working, the wf.msc shows connectivity using NTLM and Kerberos, but the clients just can't seem to stay connected on any interface.
However, in the wf.msc when the clients are not functioning, I only ever see one NTLM entry.

LOGS:
Below is a directaccess client log pulled from a non-functioning client before making any changes or any testing. Feel free to ask for the rest of the log if needed-- I have put in place holders for information that may be sensitive. Thank you!!
RED: Corporate connectivity is not working.
Windows is unable to relocationve corporate network names. Please contact your administrator if this problem persists.
24/3/2015 18:21:43 (UTC)
Probes List
FAIL PING: location-dc.domain.local
FAIL PING: location-file.domain.local
DTE List
PASS PING: 2002:'mac':5a1c::'mac':5a1c
PASS PING: 2002:'mac':5a1d::'mac':5a1d
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : c2075
Primary Dns Suffix . . . . . . . : domain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.local
domain2.ad
System Quarantine State . . . . . : Not Restricted
Wireless LAN adapter Wireless Network Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
Physical Address. . . . . . . . . : 2A-B2-BD-'mac2'-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 2A-B2-BD-'mac2'-E6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 28-B2-BD-'mac2'-E9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7260
Physical Address. . . . . . . . . : 28-B2-BD-'mac2'-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2602:304:'mac3':d370:5a1:c77:834:86a9(Preferred)
Temporary IPv6 Address. . . . . . : 2602:304:'mac3':d370:f9ce:db89:87ad:'mac4'(Preferred)
Link-local IPv6 Address . . . . . : fe80::5a1:c77:834:86a9%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.86(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, March 24, 2015 1:48:21 PM
Lease Expires . . . . . . . . . . : Wednesday, March 25, 2015 1:48:21 PM
Default Gateway . . . . . . . . . : fe80::21b:5bff:febf:4f21%12
192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : domain.local
Description . . . . . . . . . . . : Intel(R) Ethernet Connection I218-LM
Physical Address. . . . . . . . . : 28-D2-44-C5-24-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.attlocal.net:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter iphttpsinterface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : iphttpsinterface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{FD31098B-E475-49A1-9AFA-8C43FF928F97}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.domain.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:'mac':5a1c:342d:25dd:b4e1:12c8(Preferred)
Link-local IPv6 Address . . . . . : fe80::342d:25dd:b4e1:12c8%18(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{E1BE09BA-B38B-4F87-8893-E3D32A88EDFC}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{0C04B587-7861-4D8D-9DA9-6326AB71D701}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh int teredo show state
Teredo Parameters
Type : client
Server Name : 204.16.90.28 (Group Policy)
Client Refresh Interval : 30 seconds
Client Port : unspecified
State : qualified
Client Type : teredo host-specific relay
Network : unmanaged
NAT : restricted
NAT Special Behaviour : UPNP: No, PortPreserving: Yes
Local Mapping : 192.168.1.86:55842
External NAT Mapping : 75.30.237.55:55842
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh int httpstunnel show interfaces
Interface IPHTTPSInterface (Group Policy) Parameters
Role : client
URL : https://uag.webdomain.com:443/IPHTTPS
Last Error Code : 0x0
Interface Status : IPHTTPS interface deactivated
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh dns show state
Name Relocationution Policy Table Options
Query Failure Behavior : Always fall back to LLMNR and NetBIOS
if the name does not exist in DNS or
if the DNS servers are unreachable
when on a private network
Query Relocationution Behavior : Relocationve only IPv6 addresses for names
Network Location Behavior : Let Network ID determine when Direct
Access settings are to be used
Machine Location : Outside corporate network
Direct Access Settings : Configured and Enabled
DNSSEC Settings : Not Configured
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh name show policy
DNS Name Relocationution Policy Table Settings
(ENTRIES OMITTED TO SAVE SPACE)
Settings for .domain.local
Certification authority : DC=local, DC=domain, CN=HDT CA
DNSSEC (Validation) : disabled
DNSSEC (IPsec) : disabled
DirectAccess (DNS Servers) : 2002:'mac':5a1d::'mac':5a1d
DirectAccess (IPsec) : disabled
DirectAccess (Proxy Settings) : Bypass proxy
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh name show effective
DNS Effective Name Relocationution Policy Table Settings
(ENTRIES OMITTED TO SAVE SPACE)
Settings for .domain.local
Certification authority : DC=local, DC=domain, CN=HDT CA
DNSSEC (Validation) : disabled
IPsec settings : disabled
DirectAccess (DNS Servers) : 2002:'mac':5a1d::'mac':5a1d
DirectAccess (Proxy Settings) : Bypass proxy
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh int ipv6 show int level=verbose
Interface Loopback Pseudo-Interface 1 Parameters
IfLuid : loopback_0
IfIndex : 1
State : connected
Metric : 50
Link MTU : 4294967295 bytes
Reachable Time : 40000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : disabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Wireless Network Connection Parameters
IfLuid : wireless_0
IfIndex : 12
State : connected
Metric : 25
Link MTU : 1472 bytes
Reachable Time : 1101000 ms
Base Reachable Time : 1805000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 64
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.attlocal.net Parameters
IfLuid : tunnel_4
IfIndex : 22
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 27500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Wireless Network Connection 2 Parameters
IfLuid : wireless_5
IfIndex : 15
State : disconnected
Metric : 5
Link MTU : 1500 bytes
Reachable Time : 24000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface iphttpsinterface Parameters
IfLuid : tunnel_5
IfIndex : 17
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 31500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : enabled
Other Stateful Configuration : enabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Local Area Connection Parameters
IfLuid : ethernet_6
IfIndex : 11
State : disconnected
Metric : 5
Link MTU : 1500 bytes
Reachable Time : 31500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface 6TO4 Adapter Parameters
IfLuid : tunnel_6
IfIndex : 19
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 39500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : disabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.{FD31098B-E475-49A1-9AFA-8C43FF928F97} Parameters
IfLuid : tunnel_7
IfIndex : 21
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 33000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.domain.local Parameters
IfLuid : tunnel_8
IfIndex : 39
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 36000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Bluetooth Network Connection Parameters
IfLuid : ethernet_9
IfIndex : 14
State : disconnected
Metric : 50
Link MTU : 1500 bytes
Reachable Time : 17000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Wireless Network Connection 3 Parameters
IfLuid : wireless_9
IfIndex : 16
State : disconnected
Metric : 5
Link MTU : 1500 bytes
Reachable Time : 17000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Teredo Tunneling Pseudo-Interface Parameters
IfLuid : tunnel_9
IfIndex : 18
State : connected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 14500 ms
Base Reachable Time : 15000 ms
Retransmission Interval : 2000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : enabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.{E1BE09BA-B38B-4F87-8893-E3D32A88EDFC} Parameters
IfLuid : tunnel_10
IfIndex : 20
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 41000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.{0C04B587-7861-4D8D-9DA9-6326AB71D701} Parameters
IfLuid : tunnel_11
IfIndex : 23
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 40000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh advf show currentprofile
Private Profile Settings:
State ON
Firewall Policy BlockInbound,AllowOutbound
LocalFirewallRules N/A (GPO-store only)
LocalConSecRules N/A (GPO-store only)
InboundUserNotification Enable
RemoteManagement Disable
UnicastResponseToMulticast Enable
Logging:
LogAllowedConnections Disable
LogDroppedConnections Disable
FileName %systemroot%\system32\LogFiles\Firewall\pfirewall.log
MaxFileSize 4096
Ok.
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh advfirewall monitor show consec
Global Settings:
IPsec:
StrongCRLCheck 0:Disabled
SAIdleTimeMin 5min
DefaultExemptions ICMP
IPsecThroughNAT Never
AuthzUserGrp None
AuthzComputerGrp None
StatefulFTP Enable
StatefulPPTP Enable
Main Mode:
KeyLifetime 60min,0sess
SecMethods DHGroup2-AES128-SHA256,DHGroup2-AES128-SHA1,DHGroup2-3DES-SHA1
ForceDH No
Categories:
BootTimeRuleCategory Windows Firewall
FirewallRuleCategory Windows Firewall
StealthRuleCategory Windows Firewall
ConSecRuleRuleCategory Windows Firewall
Quick Mode:
QuickModeSecMethods ESP:SHA1-None+60min+100000kb,ESP:SHA1-AES128+60min+100000kb,ESP:SHA1-3DES+60min+100000kb,AH:SHA1+60min+100000kb
QuickModePFS None
Security Associations:
Main Mode SA at 03/24/2015 14:21:44
Local IP Address: 2602:304:'mac3':d370:f9ce:db89:87ad:'mac4'
Remote IP Address: 2002:'mac':5a1d::'mac':5a1d
Auth1: ComputerCert
Auth2: UserNTLM
MM Offer: None-AES128-SHA256
Cookie Pair: 9398e38420480425:51071d5bae9eb503
Health Cert: No
Quick Mode SA at 03/24/2015 14:21:44
Local IP Address: 2602:304:'mac3':d370:f9ce:db89:87ad:'mac4'
Remote IP Address: 2002:'mac':5a1d::'mac':5a1d
Local Port: Any
Remote Port: Any
Protocol: Any
Direction: Both
QM Offer: ESP:SHA1-AES192+60min+100000kb
PFS: None
Thanks again,

JMS Demo Not working!!!Very poor samples from Oracle.

Hi i have installed the CHat JMS Sample into Oc4j.
Everything was OK until i wanted to log into the chat application.
Then on my oc4j consol the following occured:
03/10/04 14:49:08 javax.jms.JMSException: TopicConnection[Oc4jJMS.Connection.bak
desktop.e06940:f807230602:-8000.9]: cannot invoke method "setClientID" within th
e J2EE container.
03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1
920)
03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.toJMSException(JMSUt
ils.java:2003)
03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.toJMSException(JMSUt
ils.java:1969)
03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.assertNotContainer(J
MSUtils.java:2427)
03/10/04 14:49:08 at com.evermind.server.jms.EvermindConnection.setClientI
Can anyone help? It is very sad because i experienced that most samples will not work if you only follow the install manual.
regads,
attila

Hello Attila,
It seems that you are using OC4J 10G to run the sample. The sample has been tested on OC4J 904 Developers preview. Please use this to run the sample application.
This demo uses JMS 1.0 and OC4J 10G supports JMS 1.1. In JMS 1.1, you cannot call setClientID() directly within the J2EE container. Due to this inherent change in the spec, the Chat Demo does not work properly in OC4J 10G.
This is a known problem and we are working on rectifying this.
Thanks,
Rajat

JMS Bridge not Working

Hi,
I have a weblogic 9.2 running one application.
I what that application to post messages on a internal JMS queue. That message gets fw to a Weblogic 8 JMS queue.
To achieve this I created a JMS Bridge with the Weblogic 8 destination, and the Weblogic 9 source.
When i activate the bridge, i did not see anything on the logs, so i restarted the server.
Once the server was Up I went to check how many consumers where register on my internal queue, and to my surprise there where none.
I posted a message to that queue and still nothing. not even on the logs.
On the source and destination, i put the following:
Adapter JNDI Name: the XA one
Classpath: weblogic.jar
Connection URL: t3://172.16.76.28:8001 on the internal and t3://172.16.76.29:7001 on the external
weblogic.jndi.WLInitialContextFactory: weblogic.jndi.WLInitialContextFactory
and the JNDI stuff, user and password.
I do not see anything in the logs. Any idea?

I would like to make sure that I understand where you are now.
1. The bridge is always running on 9.2.
2. When the bridge is configured to forward messages from local (9.2) to remote (8.1), everything works.
3. When the bridge is configured to forward messages from remote to local, you run into the SecurityException.
Is my understanding correct? Where did you see the Exception (on the 9.2 side or the 8.1 side)?
Are you always using the adapter from the same release as the server that is running the bridge?
Assuming that you have configured everything correctly, I don't see why remote-to-local case does not work for you. There was an issue similar to what you are seeing in 8.1 GA, which has been fixed in 8.1SP1 and 9.2. You should not see this issue as long as your bridge is running on 9.2 (or 8.1SP1) or later.
At this point you could try the following:
1. Change the bridge to run in sync mode (by setting AsyncEnabled to false, the default is true) and see if the problem persists.
2. Enable domain trust on both the 9.2 and 8.2 domains (see http://edocs.bea.com/wls/docs92/bridge/wls_interop.html#wp1126213 for details).
3. Run the bridge on 8.1 (using the 8.1 adapter) to forward messages to 9.2. (I know the doc recommends that one should run the bridge on the later version of WebLogic when forwarding between two different releases, but it does not hurt to try as long as your source destination is on the same release are the bridge).
Thanks,
Dongbo

Sender JMS Connectivity not working

Similar Messages

Maybe you are looking for