OOB management with console port

I would like to do the setup according to the doc - http://www.cisco.com/en/US/tech/tk801/tk36/technologies_tech_note09186a00800941c9.shtml
The only disadvantage I see is from the following excerpt from the article -
"Warning: Unprotected modems should not be connected to the console port. The console ports do not log users off when the carrier detect is lost, which can leave a security hole. To avoid this, use a secure modem, or connect via the AUX port. For more information on the advantages and disadvantages of connecting a modem to the Console port, refer to the Modem-Router Connection Guide."
I know I could set an exec-timeout of 1 minute but that would still leave a small window of time for security breaches if the line drops.
Could someone tell me a particular modem that has a password built into it to overcome this problem? What is the best security practice in this case?
I have setup modems before on the aux port, but you cannot access the router after reload if it boots into ROMMON mode for some reason.
Thanks,
RJ

Hi,
As a workaround you can try using an old junk PC with 2 serial ports, install Linux on that PC, connect via terminal session using the modem attached to serial COM1 (modem in autoanswer mode just like you're doing now), login with username/password on the Linux machine and then use a terminal emulation software like Minicom to open serial port COM2 to get the IOS prompt from the router.
Maybe this option is too much hassle for your application, but it won´t cost you a dime and is not really that difficult.
Regards.

Similar Messages

Difference between console port and dedicated management port

Can someone explain what the difference is between the console port and the dedicated management port(fa0) , on a Cisco 2960s switch.
Thank You.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
A console port is special for two reasons. First, it's "known" to the system as its console port which means the system will send status information to it, and often treat it special when accepting input. Second, the console port is generally wired as a serial port. (It also normally doesn't have an IP address.)
The console port was intended for where the system operator controls the system from, usually nearby (physically). (Console ports are/were used for any computer based system.)
Management ports are generally for remote management using an Ethernet port. On older switches/routers, a device might be configured to use an ordinary Ethernet port for this purpose. On newer switches/routers, a Ethernet port is provided for this purpose. For these, the device may actually use different hardware for port and might treat it internally differently. For example, often the Ethernet management port is only FE, it may not have ASIC support for high speed switching, and it might be in it's own predefined VRF. Generally, a management port will have an IP address, but different from IP address spaces used by other hosts.
Out-of-the-box, a console port will allow you to configure the device, but a management port will often require some additional configuration.

How to create an rule with action to subtract from the event log of Ips manager express console?

how to create an rule with action to subtract from the event log of Ips manager express console?, some knows of has an guide?.
Thank you.
Sent from Cisco Technical Support iPad App

Hi,
http://www.cisco.com/en/US/products/sw/secursw/ps2113/products_tech_note09186a0080bc7910.shtml
HTH
Luis Silva
"If you need PDI (Planning, Design, Implement) assistance feel free to reach us"
http://www.cisco.com/web/partners/tools/pdihd.html

Cisco Unified Communications Manager Attendant Console issue with cucm ver 9.1.1

Dear support,
As we used before Cisco Unified Communications Manager Attendant Console with CUCM version 7.x as now we upgrade to version 9.1.1 and we could not be able to use this service .due to attendant console is not available with cucm versio 9.1.1.
before upgrade cucm ver 7.x from PC user maintain all contact details store with Attendant console software on his desktop PC. right now its give error unable to connect to the server. due to attendant console is not available with cucm version 9.1.1.
So how i can retrieve the user store contact details from attendant console software from his PC desktop .
so please provide you feedback highly appreciate.
Regards
syed

Dear support,
As i check this on user pc c:\program files\cisco\Unified Communications Manager Attendant Console\data\GlobalSettings.xml
I couldn't be able to retrieve the store contact data .most of the user are get effected by this service.
As we do upgrade to cucm versioun 9.1.1 to use of more services but not user are to be get effect by the attendant services like we can't use Attendant console software on CUCM 9.1.1 after upgrade......
so please advice ........... atleast we need to retrieve the user store contact data ...
Highly appreciate for your resposne .....
regards
syed

Using Import manager with XI

Hi,
I am working with Import manager without any connection with XI. So, I have created by myself a XML file and a its corresponding XSD file, and I have put the XSD file into the console using XML Schemas Table.
Finally, I choose into the MDM Import manager the next options:
 - Type: XML Schema.
 - Client System: MDM.
 - XML Schema: the XML Schema declared.
 - File name: the XML file created.
The import manager imports the XML file correctly. But, my question is:
It's the same using XI? I mean, How works MDM Import manager using XI?
For instance, If I want to work with a CRM client system:
 1. XI works with CRM and tranforms its IDocs to XML.
 2. XI puts its XML file into any folder (than doesn't correspond with the ports declared into the MDM Console).
 3. Finally, XML takes the XML file in to that folder (exactly in the same way that I did before)
 4. MDM Import manager then imports the XML file into the repository.
Is that correct or the process is absolutely different using XI?
Thanks in advance,
Marta.

Each time you create a Port in the MDM Console directories are created on the server to hold data being exported and imported via the Import Server and the Syndication Server. If you log into your server you can find these directories in a heirarchy similar to this:
/opt/MDM/Distributions/ServerName/Repository/
So for example, a directory for one of your Ports may be:
/opt/MDM/Distributions/MDM_ORA/Material/Inbound/ECC(clientsystem)/In_ECC(portname)/
In that directory you will find several folders. One of which is the Ready folder. That is where the import server looks to find files to import. You can change the settings for the Import Server in its .ini file. This file is probably located in either your /opt/MDM folder or /opt/MDM/bin depending on how the installation was set up. There you can set how frequently you want the import server to check that port directory. If you are on unix you start the import server by navigating to the /opt/MDM/bin directory and running the command:
./mdis
Then check that it's running via command:
ps -ef | grep mdis
If you are on a Windows server you simply have to right click -> start the service in Services panel. Also make sure to check the /Exceptions folder in the port directory (same location as the Ready folder), because if the import fails, a file will show up there and lock the port from further use until that file is removed from the Exceptions folder.
Good luck
Message was edited by:
 Harrison Holland

How to start Weblogic 10.3.5 managed server on port 80

Hello,
We're trying to understand how to start Weblogic as root so we can start on port 80 on Linux. We understand that we'll use the post bind UID to run as a non-priv user. Right now in the Admin console under the managed server, Server Start properties (node manager) we have the weblogic user as the user to start the server, which works. Is this where we'd put the root user? We tried that but it fails complaining about root user didn't have permission to start the server. Can someone shed some light?
Thanks

Hi
1. You are asking for 2 things here:
a) Start Weblogic as root user ?
Before I answer this question, who (Which User) installed Weblogic Software and who created Domain. I hope its NOT root user. Usually its not preferable to use root account for this. Instead create a new user account like for example oracle or some xyz. Then login with that account. Install Weblogic and create any Domain. I would NOT prefer/recommend using root account to install weblogic. This means, I would not recommend/support to start weblogic as root user. The thing is when you install weblogic, it stores/creates lots of files/scripts. Now when you start, it has to be same user. Because at the startup, we need to read files and also CREATE lots of temp files under domain root folder. So on unix, this becomes very complex. Simple answer is if you install weblogic and domain with user say "xyz" and try to start domain with "root", you corrupted your entire domain. Some files gets changed to root user and some files just FAIL saying you do not have permissions. So its just gone. If you are a Unix Geek, do some magic and restore all permissions back.
b) Start Weblogic at Port 80
Very Simple. Forget about above thing. Install Weblogic and create domain say with user "xyz". Just go to domain root folder, open config/config.xml file and edit the localport to 80. By default at time of domain creation if you used all the defaults like port 7001, then you will NOT see this entry in config.xml file. But still you can edit config.xml file manually. Stop the servers. Add a section with listen-port as 80. Just refer docs for the steps. After this change, your weblogic server is now running at port 80. NOW, the main precautions is make sure that you do NOT have any other stuff running at the same port 80. Otherwise, Weblogic server startup will fail saying port 80 is already is in use.
Now if you want both a) and b), still it is possible. But I would NOT want/recommend a), which is use "root" account to install weblogic server and create and start the Domain. Nope, totally not recommending and supporting this. Yes, port 80 can be used, but not the "root" account.
Thanks
Ravi Jegga

Catalyst switch hangs when connecting via console port

Hi,
I've just started work for a company - they have no network documentation or knowledge of their current set-up whatsoever.
For the LAN in the office they have Cisco Catalyst WS-C3524-XL switches. But it doesn't seem like these are even configured with an IP address for management purposes.
So, I thought I would connect via a console cable to have a look at their configurations and also to investigate some performance problems some users were having on the LAN.
BUT - when I connected to the console cable, all the switch LEDs stopped flickering happily and went solid and everyone in the office lost their network connectivity! (I wasn't popular!)
Rebooting the switch with the console port still connected had no effect - the LEDs remained solid and there was no network connectivity. However, when I removed my console cable, everything started working again!
Does anyone have any ideas a) what can have caused this and b) how I can resolve this problem and connect to the switches without disrupting all the other users!
Note: I subsequently connected to a spare WS-C3524-XL switch using the same laptop and same console cable without any problems.

Hi,
thanks for the response.
no, I can't login to the switch(es) at all. There seems to be no response from hyperterminal at all. (Then I noticed that the LEDs had gone "solid" and that everyone started to complain they had lost network connection!)
Even when I powered off and powered on the switch with the console port still connected, nothing appeared on the hyperterminal screen.
However, as mentioned, I'm able to connect to one of our spare switches using the same settings, same laptop, and same console cable - so I guess that would rule these things out as being the cause?
Its definitely a strange one, especially as it seems to be affecting all 3 of the live switches!

Conect two routers over console port

Hi Guys ,
How conect two routers or firewall over console port for manager ?
Thanks
Jorge

Hi Jorge,
I do not believe that you can connect to devices over console ports.
I have in the past connected from an aux port on a router to a console port on a switch using one of the old RJ45-RJ45 rollover cables Cisco used to ship with DB9-RJ45 adapters before they starting shipping DB9-RJ45 console cables.
You should be able to use the configuration in the document at the link below as a starting point.
http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a008014f8e7.shtml
This document is for a terminal server with 16 async ports. The config below should be ok for an aux port.
ip host switch 2001 172.21.1.1
interface Loopback1
ip address 172.21.1.1 255.0.0.0
line aux 0
session-timeout 20
no exec
exec-timeout 0 0
Please rate if helpful.

OoB Problems with SCCM 2012 SP1 CU1

Hi around, perhaps somone has tried this things out already and has a little hint for me.
After we got OoB Managment to work under SCCM 2007 we switched to SCCM 2012 now i have some problems bringing it to work again.
We use a Verisign Certificate for Provisioning, the Firewall Ports (9971 on Server and 19992, 16993 and 16995 on Client) are opend. The autoenrollment is active. DHCP 06 and 15 are set and configured.
The IIS SSL Settings are configured to accept Client Certificates and the Bindings are set to the Web Server Template. We tried to configure it using the Verisign Certificate but it didn't work that way either.
The Webserver Template is build after the Step by Step guide from MS.
The Verisign Certificate was build the same way, Organization Unit is set to Intel(R) Client Setup Certificate. It was imported in the Personal Certificate Store, exported and implemented in the Enrollment Point.
The AD Group exists and the Oob Managment Server has the permissions it needs.
The Oob Managment Point was configured like shown in the MS Step by Step guide.
The Client i'm testing with was fully unprovisioned.
Now the only Status i get is detected and when i try to discover AMT the amtopmgr.log brings the following errors.
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
**** Error 0x1e5ab3d0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
**** Error 0x1e5ab3d0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://OurMachine.test.de:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://OurMachine.test.de:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://OurMachine.test.de:16993 , 484001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoKerberosWSManDiscovery failed. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://10.37.135.52:16993 , 15001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://10.37.135.52:16993 , 15001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Discovery to IP address 10.37.135.52 succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CSMSAMTDiscoveryTask::Execute, discovery to OurMachine succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CSMSAMTDiscoveryTask::Execute - DDR written to D:\CM2012\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='OurMachine.test.de' P2='' P3='' P4='' P5='' SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CStateMsgReporter::DeliverMessages - Created state message file: D:\CM2012\inboxes\auth\statesys.box\incoming\vww2tcjc.SMX SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Succeed to run the task OurMachine.test.de. Remove it from task list. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Work thread 3624 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Work thread 3624 exiting. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Current size of the thread pool is 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 9236 (0x2414)
We double checked the admin Account in the OOB settings but the password is right and i can manually log in to the MEBX with it.
Has anyone some suggestions what could be wrong?
Thank's for the help.

Yes, I know this is an old post, but I’m trying to clean them up.
Did you solve this problem, if so what was the solution?
By the sounds of thing the problem is with your certificate. Can you manually provision a Certified to any of these systems?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Unable to log-in in Oracle Identity Manager Design Console

Hello,
I successfully installed OIM9.1.0.1 Identity Manager on Jboss4.2.3.GA App server and could login to OIM using http://llocalhost:8080/xlWebApp on my window Server 2003 system without any problem.
Then I installed the Design Console on my window XP system. However, after successfully installing the Design Console, I could not login using the xelsysadm user ID.
I checked to make sure that xlconfig.xml contains the right URL file under oim_designConsole directories.
The error I get from the Design Console login window is:
Internal Login
Oracle Identity Manager Design Console Could not log you in.
In the dos-command window, I got the error:
WARN,22 Apr 2009 16:31:52,160,[org.jboss.remoting.marshal.MarshalFactory],Could
not find marshaller for data type 'invocation'. Object in collection is null
WARN,22 Apr 2009 16:31:52,160,[org.jboss.remoting.marshal.MarshalFactory],Found
marshaller fully qualified class name within locator parameters, but was unable
to load class: org.jboss.invocation.unified.marshall.InvocationMarshaller
WARN,22 Apr 2009 16:31:52,160,[org.jboss.remoting.marshal.MarshalFactory],Could
not find marshaller for data type 'invocation'. Object in collection is null
java.lang.reflect.UndeclaredThrowableException
at $Proxy0.create(Unknown Source)
at com.thortech.xl.dataaccess.tcDataBaseClient$1.run(Unknown Source)
at Thor.API.Security.LoginHandler.jbossLoginSession.runAs(Unknown Source
at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown So
urce)
at com.thortech.xl.dataaccess.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.server.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.client.dataobj.tcDataBaseClient.<init>(Unknown Source
at com.thortech.xl.client.base.tcAppWindow.internalLogin(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.login(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.<init>(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.main(Unknown Source)
Caused by: org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a
valid marshaller for data type: invocation
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.jav
a:78)
at org.jboss.remoting.Client.invoke(Client.java:226)
at org.jboss.remoting.Client.invoke(Client.java:189)
at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(Un
ifiedInvokerProxy.java:184)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerIntercep
tor.java:227)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.jav
a:167)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.
java:46)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:5
5)
at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:169)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
I would really appreciate your help in this regards.
Thanks for helping me resolve this issue.
Regards,
Dhirendra

vBackup the original file log4j-1.2.8.jar in oimclient/xlclient/ext
copy the log4j.jar from JBOSS folder - JBOSS/server/default
Paste the file in client folder with original log4j-1.2.8.jar
Rename log4j.jar file to log4j-1.2.8.jar
start ur JBOSS.. this shd work.

CUCM 8.6 Manager Assistant Console

I am currently setting up a test setup of the Manager Assistant Console in proxy mode and have a few questions about the proxy lines and the intercom lines.
In the setup guide, Manager and Assistant Phone Configurations tell you to configure the phones with the following setting: (We have 7962 phones)
"If using the Cisco Unified IP Phone 7900 series, except Cisco Unified IP Phone 7940 or 7960, configure the intercom feature "
I assumed that these were standard intercoms like I had set up for some other Managers in the past. I had gone to "Call Routing>Intercom" and set up an intercom partition (Intercom1), a CSS (Intercom 1 CSS, includes ONLY the Intercom1 partition), and several DN's for intercoms (3-digits and out of range of our regular 5-digit DN's on phones). Then I created some custom phone button templates that included one intercom line in addition to the phone lines. This keeps intercoms lines separate from regular DN's so users can't call someone's intercom line as if it were a regular DN and they use the whisper mode by default placing the receiving phone in speaker mode but muted so the caller cannot surreptitiously listen in on someone else.
So, this is what I did also for the manager and assistant phones for use with the Assistant console. Simply created some more Intercom DN's and assigned them to the Manager and Assistant Phones using custom button templates that include a 'real' Intercom Line.
Everywhere else that talks about the intercom lines for the Manager Assistant Console seems to indicate that they are not 'real' intercom lines but simply regular DN's that have "Auto Answer w/ Speaker" turned on and are in the ONNET (everyone) partition. This means that there is no Whisper feature and the assistant (or anyone who knows the managers 'intercom DN' can spy on the manager. This is totally unacceptable.
I think I can configure this using 'real' Intercom lines that have their own partition (so only other intercom users can reach it) and have the whisper feature (auto answer w/ speakerphone BUT MUTED) except when it comes to the IPMA Clusterwide Parameter, "All User Partition" that is supposed to be configured with the name of the partition that includes the Intercom DN's AND the Proxy DN's.
The two possible solutions I can see are:
1. The Clusterwide Parameter is only for Automatic Configuration and I am manually configuring everything so maybe I don't have to configure this parameter while just using 'real' Intercoms in the Intercom1 partition while setting up proxy lines in the ONNET partition
OR
2. I might be able to configure the proxy DN's to use the Intercom partition instead of the ONNET partition.

The answer turned out to be 1. You can use real intercom lines just fine and in fact they have several advantages.
1. By using real intercom lines you initially get the one-way Whisper mode and the called party can press a button to go two way. The IPMA way are two-way only.
2. By using real intercom lines they stay intercom lines even when the assistant is logged out. The IPMA way causes the intercom lines to revert to normal phone lines when the assistant logs out.

Front end and console ports are down for switch WS-C3750X-48PF-S

We have a switch WS-C3750X-48PF-S in the stack and front end and console ports stopped working and are down.
I have tried to replug power cable but this didn't help, please let me know if I could replug stack power for this switch without outage of other switches in the stack, since switches are connected into the ring
Please let me know what might be the possible root cause
#sh switch stack-ports
  Switch # Port 1 Port 2
    2 Down Ok
    3 Ok Ok
    4 Ok Down

Hello,
There is a problem with the stacking connection between switch 4 and 2. Can you try replacing the stacking cable between these switches?

How to install Oracle BPEL Process Manager with the BEA WebLogic

Hi ,
I will install Oracle BPEL Process Manager with BEA WebLogic 9.2(MP2). I have download orabpel_10133_WebLogic.zip ,then Modify the following mandatory installation properties in the orabpel_10133_WebLogic\bpelDomain.properties file:
# BEA_HOME is the path where Weblogic is Installed
BEA_HOME=/opt/bea
# JAVA_HOME is the path of jdk folder inside your weblogic
JAVA_HOME=/opt/bea/jrockit90_150_10
# DOMAIN_HOME is the path where you wish to create your domain called BPELDomain
DOMAIN_HOME=/opt/bea/user_projects/domains
# APPS_HOME is the path where you wish to copy your applications and adapters that are required for oracleBPELServer
APPS_HOME=/opt/bea/user_projects/apps
# BEA_HOME is the path where BPEL PM is Installed
BPEL_HOME=/home/oracle/bpel/product/10.1.3.1/OraBPEL_1/bpel
# DRIVER_TYPE is the datasource class that installable use to create a datasources for oracleBPELServer
DRIVER_TYPE=oracle.jdbc.xa.client.OracleXADataSource
# DB_URL is the url to connect to orabpel schema
DB_URL=jdbc:oracle:thin:@16.157.134.17:1521:orcl
# DB_USER is the user Id for orabpel shema in database
DB_USER=ORABPEL
#DB_PASSWORD is the password for orabpel schema in database
DB_PASSWORD=bpel
#BPEL_SERVER_NAME is the server i.e. to be created under BPELDomain
BPEL_SERVER_NAME=oracleBPELServer
#PROXY_HOST is the Host name of the proxy server
PROXY_HOST=www-proxy.us.oracle.com
#PROXY_HOST=
#PROXY_PORT is the Port where the proxy server is running
PROXY_PORT=80
#PROXY_PORT=
#NON_PROXY_HOST is the list of non proxy hosts that are divided by a | symbol
#NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com
NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com|16.157.134.135
When I run the setup.sh , it will report
BUILD FAILED
/opt/software/WL_Installables/build.xml:131: Traceback (innermost last):
File "./wl_scripts/bpelDomain.py", line 22, in ?
File "./wl_scripts/createGroupsAndUsers.py", line 4, in ?
weblogic.management.utils.AlreadyExistsException: [Security:090267]Group BpelGroup
Actully ,there is no BpelGroup in Weblogic. Does anybody know how to solve it ?

MAke sure you have not set ANY environment variable related to Oracle / BEA / Java / LD_library path. Use the following script to unset / set the initial settings:
#!/bin/sh
unset ORACLE_BASE ORACLE_HOME ORACLE_SID ORACLE_TERM
unset LD_LIBRARY_PATH LD_LIBRARY_PATH_64
unset CLASSPATH JAVA_HOME
export PATH=.:/usr/sbin:/usr/bin:/usr/local/bin:/opt/VRTS/bin
export BEA_HOME=/appl/oracle/products/9.2/weblogic
Marc
http://orasoa.blogspot.com

Not able to start the Sun Java System Access Manager 7 Console

Hi All,
I have successfully installed the Sun Java System Portal Server 7 on RHEL 4.0.The problem I am facing is not able to start the Sun Java System Access Manager 7 Console while accessing the URL: http://fqdn:8080/amconsole
As soon as I try to access this URL it gives me following Excepiton:::::::
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
com.iplanet.jato.NavigationException: Exception encountered during forward
Root cause = [java.lang.NullPointerException]
     com.iplanet.jato.view.ViewBeanBase.forward(ViewBeanBase.java:386)
     com.iplanet.jato.view.ViewBeanBase.forwardTo(ViewBeanBase.java:267)
     com.iplanet.am.console.base.ConsoleServletBase.onUncaughtException(ConsoleServletBase.java:338)
     com.iplanet.jato.ApplicationServletBase.fireUncaughtException(ApplicationServletBase.java:1023)
     com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:469)
     com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
     com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:294)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:585)
     org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     java.security.AccessController.doPrivileged(Native Method)
     javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
If anyone have any idea about the cause of this error,please let me know.All suggestions are welcome .
Thanx and Regards,
Chirag.

Hi All,
I am having exactly the same problem with the same stack trace. Has anybody have an idea how to fix this?
I have downloaded the Java Identity Management Suite.(java_es-5-identsuite-ga-windows-x86.zip) The first time installation was fine and I was able to bring the Access Manager console. I was able to create users groups etc.
However, when I uninstalled and installed it again, I got exactly the same error described in the thread. Running "amserver start" and "amserver restart" did not help. I did the installation one more time
but again I got the same error.
Thanks for the help.
celikkan

MQSeries as a Transactional Resource Manager with Weblogic Server

 I am trying to setup the example given in the BEA white paper:
 Using MQSeries as a Transactional Resource Manager with Weblogic Server.
 Version 1.
 October 25, 2001.
 I followed the instructions given in the documents, but when i run client program
 >java MQClient t3://localhost:7001 "MQSeries test"
 I received the following exception below. Does anyone how what is the reason for
 this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
 for java and the MQSeries classes for Java Message Service on the weblogic
 server machine.
 sending: "MQSEries test"
 Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
 sted exception is:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 Start server side stack trace:
 java.rmi.ServerError: A error occurred the server; nested exception is:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 at java.lang.System.loadLibrary(System.java:820)
 at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 149)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 a:80)
 at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 ctionManager.java:150)
 at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 a:666)
 at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 AQueueConnectionFactory.java:53)
 at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 a:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 .java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 ; nested exception is:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 Start server side stack trace:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 at java.lang.System.loadLibrary(System.java:820)
 at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 149)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 a:80)
 at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 ctionManager.java:150)
 at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 a:666)
 at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 AQueueConnectionFactory.java:53)
 at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 a:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 .java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 Start server side stack trace:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 at java.lang.System.loadLibrary(System.java:820)
 at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 149)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 a:80)
 at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 ctionManager.java:150)
 at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 a:666)
 at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 AQueueConnectionFactory.java:53)
 at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 a:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 .java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 <<no stack trace available>>
 --------------- nested within: ------------------
 weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
 [java.rmi.ServerError: A error occurred the server; nested exception is:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 Start server side stack trace:
 java.rmi.ServerError: A error occurred the server; nested exception is:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 at java.lang.System.loadLibrary(System.java:820)
 at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 149)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 a:80)
 at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 ctionManager.java:150)
 at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 a:666)
 at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 AQueueConnectionFactory.java:53)
 at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 a:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 .java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 ; nested exception is:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 Start server side stack trace:
 java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 at java.lang.System.loadLibrary(System.java:820)
 at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 149)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 a:80)
 at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 ctionManager.java:150)
 at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 a:666)
 at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 AQueueConnectionFactory.java:53)
 at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 a:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 .java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
 at $Proxy1.bridgeWLS2MQS(Unknown Source)
 at MQClient.main(MQClient.java:54)


The point is that over TCPIP the MQ XA connection factory is not available.
 The MQ shared memory/JNI driver is required to access it, which limits
 access to those processes that are on the same box as the MQ q manager.
 This is an MQ series limitation.
 Douglas WF Acheson wrote:
 > Hello,
 >
 > If memory server me correct, default connection to MQ Series is through
 > JNI calls and shared memory. You have to change the protocol to TCPIP when
 > connection to the queue manager on another box (do not know much about XA
 > with MQ Series); that is when you connect to MQ Series vi JMS on another
 > box you must do something like the following:
 >
 > qcf = new MQQueueConnectionFactory() ;
 > qcf.setHostName(hostName) ;
 > qcf.setPort(port) ;
 > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
 > qcf.setQueueManager(qManagerName) ;
 >
 > Then when you create you queues, sesions etc. you are point at the correct Q
 > manager.
 >
 > Hope this helps ...
 >
 > Douglas WF Acheson
 >
 > "Raja Mukherjee" <[email protected]> wrote in message
 > news:[email protected]...
 > > On a closer look at the original post (sorry for missing that, it was
 > early
 > > in the morning), you would not be able to use XA if your QM and WLS are in
 > > different boxes. Check on this newsgroup, there are several posts on this
 > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
 > on
 > > the sames box. This is a MQSeries limitation not WLS.
 > >
 > > .raja
 > >
 > >
 > > "ibrahim Nehme" <[email protected]> wrote in message
 > > news:[email protected]...
 > > >
 > > > I am trying to setup the example given in the BEA white paper:
 > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
 > > > Version 1.
 > > > October 25, 2001.
 > > > I followed the instructions given in the documents, but when i run
 > client
 > > program
 > > >
 > > > >java MQClient t3://localhost:7001 "MQSeries test"
 > > > I received the following exception below. Does anyone how what is the
 > > reason for
 > > >
 > > > this exception(s) and how i can solve the problem? My MQSeries Server
 > and
 > > Weblogic
 > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
 > > classes
 > > > for java and the MQSeries classes for Java Message Service on the
 > weblogic
 > > > server machine.
 > > > ---------------------------------------
 > > > sending: "MQSEries test"
 > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
 > > server; ne
 > > > sted exception is:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > >
 > > > Start server side stack trace:
 > > > java.rmi.ServerError: A error occurred the server; nested exception is:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 > > > at java.lang.System.loadLibrary(System.java:820)
 > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 > > > at java.security.AccessController.doPrivileged(Native Method)
 > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 > > > at
 > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 > > > at
 > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 > > > 149)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 > > > at
 > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 > > > a:80)
 > > > at
 > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 > > > ctionManager.java:150)
 > > > at
 > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 > > > a:666)
 > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 > > > at
 > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 > > > )
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 > > > AQueueConnectionFactory.java:53)
 > > > at
 > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 > > > at
 > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 > > > a:267)
 > > > at
 > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 > > > java:22)
 > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 > > > End server side stack trace
 > > > ; nested exception is:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > >
 > > > Start server side stack trace:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 > > > at java.lang.System.loadLibrary(System.java:820)
 > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 > > > at java.security.AccessController.doPrivileged(Native Method)
 > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 > > > at
 > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 > > > at
 > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 > > > 149)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 > > > at
 > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 > > > a:80)
 > > > at
 > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 > > > ctionManager.java:150)
 > > > at
 > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 > > > a:666)
 > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 > > > at
 > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 > > > )
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 > > > AQueueConnectionFactory.java:53)
 > > > at
 > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 > > > at
 > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 > > > a:267)
 > > > at
 > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 > > > java:22)
 > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 > > > End server side stack trace
 > > >
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > >
 > > > Start server side stack trace:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 > > > at java.lang.System.loadLibrary(System.java:820)
 > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 > > > at java.security.AccessController.doPrivileged(Native Method)
 > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 > > > at
 > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 > > > at
 > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 > > > 149)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 > > > at
 > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 > > > a:80)
 > > > at
 > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 > > > ctionManager.java:150)
 > > > at
 > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 > > > a:666)
 > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 > > > at
 > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 > > > )
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 > > > AQueueConnectionFactory.java:53)
 > > > at
 > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 > > > at
 > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 > > > a:267)
 > > > at
 > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 > > > java:22)
 > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 > > > End server side stack trace
 > > >
 > > > <<no stack trace available>>
 > > > --------------- nested within: ------------------
 > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
 > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > >
 > > > Start server side stack trace:
 > > > java.rmi.ServerError: A error occurred the server; nested exception is:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 > > > at java.lang.System.loadLibrary(System.java:820)
 > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 > > > at java.security.AccessController.doPrivileged(Native Method)
 > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 > > > at
 > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 > > > at
 > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 > > > 149)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 > > > at
 > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 > > > a:80)
 > > > at
 > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 > > > ctionManager.java:150)
 > > > at
 > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 > > > a:666)
 > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 > > > at
 > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 > > > )
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 > > > AQueueConnectionFactory.java:53)
 > > > at
 > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 > > > at
 > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 > > > a:267)
 > > > at
 > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 > > > java:22)
 > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 > > > End server side stack trace
 > > > ; nested exception is:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > >
 > > > Start server side stack trace:
 > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
 > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
 > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
 > > > at java.lang.System.loadLibrary(System.java:820)
 > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
 > > > at java.security.AccessController.doPrivileged(Native Method)
 > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
 > > > at
 > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
 > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
 > > > at
 > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
 > > > 149)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
 > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
 > > > at
 > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
 > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
 > > > at
 > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
 > > > a:80)
 > > > at
 > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
 > > > ctionManager.java:150)
 > > > at
 > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
 > > > a:666)
 > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
 > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
 > > > at
 > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
 > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
 > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
 > > > at
 > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
 > > > )
 > > > at
 > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
 > > > AQueueConnectionFactory.java:53)
 > > > at
 > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
 > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
 > > > at
 > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
 > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
 > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 > > > at
 > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
 > > > a:267)
 > > > at
 > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
 > > > java:22)
 > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 > > > End server side stack trace
 > > > ]
 > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
 > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
 > > > at MQClient.main(MQClient.java:54)
 > >
 > >

OOB management with console port

Similar Messages

Maybe you are looking for