Harley Jackson

Greenhorn
+ Follow
since May 18, 2005
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by Harley Jackson

The page isn't doing anything crazy, here's what it looks like:
18 years ago
Other projects use a similar page, although not exactly. This page loads fine on websphere 5.1 as well as tomcat4 and tomcat5.
18 years ago
We're having a problem deploying our app on was 6.0. It worked fine when we were running on was 5.1, but for some reason now we cannot get the application up. There isn't anything wrong with the server, other projects have deployed their projects successfully, so I'm wondering what the issue could be.

Here is a stack trace when you hit the page:



Here is the deployment descriptor



Do you have any idea whats going wrong?

Thanks
18 years ago
Ok I found the problem. Stupud me! I didn't change the dtd in the web.xml. I used to be running on 2.3, so I had to upgrade it to 2.4.

Thanks for the help
18 years ago
JSP
I thought of that...but a strange thing, the welcome_jsp.class only has 1800 lines.
18 years ago
JSP
Hi I'm trying to get a calendar custom tag working in my project and am stuck on an issue. Its a pretty simple thing (for starters at least) in jsp2.0. I'm using spring 1.2.6 and jsp2.0 on java 1.4.2_10 using tomcat 5.5 (with the java1.4 compatability add ons of course)

Here is my tld file for this:

-----------------------------------------------
Here is my jsp:

---------------------------------------------------------------
Here is my tag file:

---------------------------------------------
So as far as I can tell this should be working. My guess though is it is having some issue with setting the JspFragment from the attributes. Any help would be greatly appreciated.

Thanks...below you will find my error stacktrace

18 years ago
JSP
Hi,

I'm on a project that uses Websphere 5.1. We've had our servers configured for a long time. We use Network deployment. Recently we've been trying to create a few test boxes for build test purposes. But the people who set up our system are gone and have left no documentation. We figured out how to create a new server instance using the wsinstance batch, but it is not appearing as a windows service as do our other server instances. Is there something else we should be doing? Or could we have created the instance improperly?

Thanks
19 years ago
Below is the section of the log from the stop onwards. The stop looks clean, but when I log onto the app servers, the service for the app server is stopped, and the node agent is running.

I will try to attach a log of starting when I get a chance to pull everyone off those environments and stop it.
[10/12/05 9:24:22:247 PDT] 55409e6f AdminHelper A ADMN1020I: Attempt made to stop the FASTServer1 server. (User ID = eagnmnsxd70:389/qdbdn0)
[10/12/05 9:24:23:201 PDT] f545e60 HttpTransport A SRVE0172I: Stopped transport http on port 9,080.
[10/12/05 9:24:23:217 PDT] f545e60 HttpTransport A SRVE0172I: Stopped transport https on port 9,443.
[10/12/05 9:24:28:458 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt3a
[10/12/05 9:24:28:458 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT3ApptCancelListenerPort stopped for JMSDestination FASTID05/JMS/APT_CNCL
[10/12/05 9:24:28:474 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT3ApptUpdateListenerPort stopped for JMSDestination FASTID05/JMS/APT_UPDT
[10/12/05 9:24:28:474 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT3ApptQueryListenerPort stopped for JMSDestination FASTID05/JMS/APT_INQR
[10/12/05 9:24:28:489 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT3ApptCreateListenerPort stopped for JMSDestination FASTID05/JMS/APT_CRTE
[10/12/05 9:24:28:489 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT3MessagingListenerPort stopped for JMSDestination FASTID05/JMS/FAST_INBOUND
[10/12/05 9:24:28:489 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT3ProfileUpdateListenerPort stopped for JMSDestination FASTID05/JMS/CUST_PROF
[10/12/05 9:24:28:489 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:28:552 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt3a] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:28:583 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt3a] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:28:614 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt3a] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:28:614 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt3a] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:28:661 PDT] f545e60 EJBContainerI I WSVR0041I: Stopping EJB jar: messaging-ejb.jar
[10/12/05 9:24:28:692 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt3a
[10/12/05 9:24:28:708 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt2d
[10/12/05 9:24:28:708 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:28:723 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2d] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:28:895 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2d] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:28:957 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2d] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:28:973 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2d] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:28:988 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt2d
[10/12/05 9:24:29:004 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt2c
[10/12/05 9:24:29:004 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:29:019 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2c] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:29:035 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2c] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:29:066 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2c] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:29:082 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2c] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:29:097 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt2c
[10/12/05 9:24:29:113 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt2a
[10/12/05 9:24:29:113 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT2ApptCancelListenerPort stopped for JMSDestination FASTID03/JMS/APT_CNCL
[10/12/05 9:24:29:113 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT2ApptQueryListenerPort stopped for JMSDestination FASTID03/JMS/APT_INQR
[10/12/05 9:24:29:113 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT2ApptCreateListenerPort stopped for JMSDestination FASTID03/JMS/APT_CRTE
[10/12/05 9:24:29:113 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT2ProfileUpdateListenerPort stopped for JMSDestination FASTID03/JMS/CUST_PROF
[10/12/05 9:24:29:129 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT2MessagingListenerPort stopped for JMSDestination FASTID03/JMS/FAST_INBOUND
[10/12/05 9:24:29:129 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT2ApptUpdateListenerPort stopped for JMSDestination FASTID03/JMS/APT_UPDT
[10/12/05 9:24:29:129 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:29:144 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2a] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:29:160 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2a] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:29:175 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2a] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:29:191 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2a] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:29:206 PDT] f545e60 EJBContainerI I WSVR0041I: Stopping EJB jar: messaging-ejb.jar
[10/12/05 9:24:29:253 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt2a
[10/12/05 9:24:29:253 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt1d
[10/12/05 9:24:29:269 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:29:269 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1d] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:29:331 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1d] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:29:362 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1d] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:29:362 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1d] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:29:378 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt1d
[10/12/05 9:24:29:394 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt1c
[10/12/05 9:24:29:394 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:29:409 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1c] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:29:425 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1c] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:29:440 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1c] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:29:440 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1c] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:29:456 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt1c
[10/12/05 9:24:29:472 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt1
[10/12/05 9:24:29:487 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:29:503 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:29:518 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:29:581 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:29:581 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:29:612 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt1
[10/12/05 9:24:29:627 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt2e
[10/12/05 9:24:29:643 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:29:674 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2e] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:29:705 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2e] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:29:737 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2e] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:29:768 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt2e] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:29:846 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt2e
[10/12/05 9:24:29:846 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: cat1
[10/12/05 9:24:29:861 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:29:877 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/cat1] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:29:892 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/cat1] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:29:986 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/cat1] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:29:986 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/cat1] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:30:002 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: cat1
[10/12/05 9:24:30:017 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: pt1a
[10/12/05 9:24:30:033 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT1ProfileUpdateListenerPort stopped for JMSDestination FASTID01/JMS/CUST_PROF
[10/12/05 9:24:30:033 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT1ApptUpdateListenerPort stopped for JMSDestination FASTID01/JMS/APT_UPDT
[10/12/05 9:24:30:033 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT1ApptCancelListenerPort stopped for JMSDestination FASTID01/JMS/APT_CNCL
[10/12/05 9:24:30:033 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT1ApptQueryListenerPort stopped for JMSDestination FASTID01/JMS/APT_INQR
[10/12/05 9:24:30:033 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT1MessagingListenerPort stopped for JMSDestination FASTID01/JMS/FAST_INBOUND
[10/12/05 9:24:30:033 PDT] f545e60 MDBListenerIm I WMSG0043I: MDB Listener PT1ApptCreateListenerPort stopped for JMSDestination FASTID01/JMS/APT_CRTE
[10/12/05 9:24:30:189 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:30:220 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1a] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:30:235 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1a] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:30:282 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1a] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:30:282 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/pt1a] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:30:345 PDT] f545e60 EJBContainerI I WSVR0041I: Stopping EJB jar: messaging-ejb.jar
[10/12/05 9:24:30:376 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: pt1a
[10/12/05 9:24:30:376 PDT] f545e60 ApplicationMg A WSVR0217I: Stopping application: t508
[10/12/05 9:24:30:391 PDT] f545e60 WebContainer A SRVE0170I: Stopping Web Module: FAST.
[10/12/05 9:24:30:407 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/t508] [Servlet.LOG]: AdminServlet: destroy
[10/12/05 9:24:30:454 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/t508] [Servlet.LOG]: BootstrapServlet: destroy
[10/12/05 9:24:30:485 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/t508] [Servlet.LOG]: SimpleFileServlet: destroy
[10/12/05 9:24:30:485 PDT] f545e60 WebGroup I SRVE0180I: [FAST] [/t508] [Servlet.LOG]: JSP 1.2 Processor: destroy
[10/12/05 9:24:30:500 PDT] f545e60 ApplicationMg A WSVR0220I: Application stopped: t508
[10/12/05 9:24:30:859 PDT] f545e60 ServerCollabo A WSVR0024I: Server FASTServer1 stopped
19 years ago
On my project, we've been experiencing a problem for a while. We are using websphere 5.1 in a clustered environment. I will use our simplest environment cause if we fix it there, it will probably be the solution to the others. We are running WAS ND, we have 1 webserver and 2 app servers. Whenever I update an application, it requres restarting the app servers. We've been having a lot of problems stopping/starting through the admin console, it takes a long time then errs out. But if we go on to the individual app servers and stop the deployment manager and app server services, then kill java processes and start everything back up...DM first, then app server. Thats how we've been doing it. My question is why is this happening? In our production environment, it doesnt work like this, and we don't control those boxes, so we can't know why, an outside group configured our boxes and as far as we know they should be the same, but obviously not. When the app server is stopped, either through the console or through services, should the java process for it still be running? Because when I try to start the server, if gives me a cannot create semephore error. My guess is that for some reason, even though the services says its started, the node agent is holding onto the process...because there are 2 java processes, one for the node agend and one for the app server. Is this the way it should be? Does anyone know how I can resolve this issue?

Thanks
19 years ago
With my current websphere setup, every time I deploy I have to bring down the services for each node on the network and restart them each time I deploy. I have 2 questions.

1) Is there any plugin I can get or special setup to where I won't have to restart the server every time I deploy code? I saw some articles on High Availibility from IBM, but those were tools on a linux environment. I am currently on a windows server.

2) When I stop the services in my production environment, the processes die. For some reason in my testing environment I have to manually kill the java processese for the services to truly be stopped. Is there any way to correct this? I didn't set these boxes up initially, so I don't know what was done differently.

Thanks
19 years ago
Your latest error has nothing to do with user name and password; the wsadmin program was unable to find the DM naming service because:
1. the DM is not running.
The DM is running....not on the build box, but there shouldnt be one running from there.

2. the provider used is incorrect (wrong host name or wrong port).
The hostname and port are correct. When I run wsadmin -conntype RMI -host ipaddr -port 9809 on the machine with the deployment manager, it connects using the user/pass

wsadmin could not find the name server so it defaulted to your local application server name server. Is the IP address in the stack trace your build machine IP address? Port 2809 is an application server bootstrap port.
Yes, the IP address in the stacktrace is my build box. Is it a problem that my build box and the deployment manager are on different networks? Is that why it can't find the name server?

Execute: wsadmin.sh -conntype RMI -host YOURHOSTNAME -port 9809 (or YOUR RMI port number)
When I execute this on the machine with the deployment manager (my appserver), It prompts a login. I enter the user/pass and it lets me into the wsadmin command prompt using the deployment manager. When I run this on my build box, it gets to the login prompt, and here is where it won't accept my user/pass.

If you can not ping YOURHOSTNAME, then substitute the DM machine's IP address.
I have been using the ip address. From the build box, I am able to successfully telnet into the 9809 and 8879 ports on the app server containing the dmngr.

That global security is enabled is new information. Make sure the user you are using is defined in WebSphere as a console user (System administration-->Console settings-->Console users).
Global security was not enabled, but the user was not present on the Console users...there weren't any. I added the user I was trying to log in as in the console users and restarted the deployment manager. I am still getting the same problem.


What is going on with the SOAP access? No other service is using the same port number as DM SOAP? Does wsadmin.traceout give you any useful information?
As for the SOAP connection: I tested to see if anything else is using port 8879, and nothing is using it. I made sure the machine is listening on that port, and it is. Here is the error made in the trace file when I run the command wsadmin -conntype SOAP -host deplyomentIP -port 8879 on the app server with the deployment manager:

7062c228 AbstractShell A WASX7326I: Loaded properties file /D:/WebSphere/DeploymentManager/properties/wsadmin.properties
7062c228 AbstractShell A WASX7093I: Issuing message: WASX7023E: Error creating SOAP connection to host DeploymentManagerIP; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException

19 years ago
Ok, there is a new issue. When I was able to connect through RMI, I was connecting from the machine that the Deployment manager was on. I'm trying to connect now from my build box to run my ant scripts, and the username and password I supplied from the actual machine aren't working. Is there some network portion of the username I'm missing? Here is the error I got:

[5/24/05 10:39:26:812 EDT] 7d57d989 WsnInitCtxFac W NMSV0602E: Naming Service unavailable. A communications error occurred.
[5/24/05 10:39:26:812 EDT] 7d57d989 SecurityServe E SECJ0252E: Error getting remote security server. The exception is javax.naming.CommunicationException: Could not obtain an initial context due to a communication failure. Since no provider URL was specified, the default provider URL of "corbaloc:iiop:[email protected]:2809/NameService" was used. Make sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. Root exception is org.omg.CORBA.COMM_FAILURE: WRITE_ERROR_SEND_1 vmcid: 0x49421000 minor code: 50 completed: No
19 years ago
Ok the port I was using for SOAP was correct, but it still isn't working. However, the RMI method was successful. Forgive my ignorance, but what is the difference between the two? Is one better than the other. Could SOAP be disabled on my machine for some reason?

Thanks again
19 years ago
The build box is not connected through a node, this is something I'm planning on doing later. I have been trying to run the wsadmin from one of the app servers just to test if I can do this, and later will add the node to my build box. And yes this is a test environment. Even when I am on the machine with the Deployment manager service, If I try to connect using SOAP it fails to connect, which I find is really odd.
19 years ago