date:20180126

Re: AJP Connector not throwing EOFException

2018-01-26 Thread Emanuel Hategan

Hi Chris,

in order to conclude on this thread could you please answer my final
question now that I understood what the source of the problem is?

So, is there is a way to have connections between apache and tomcat closed
when aborted?

I've found recovery_options 4 for ajp workers which closes the connection
to tomcat if an error when writing back the answer to the client is
detected but not sure if such a behaviour can be configured for READ.

George


On Mon, Jan 22, 2018 at 11:45 AM, Emanuel Hategan  wrote:

> Hi Chris,
>
> > Forget about EOFException, that was my mistake in the first email
>> > (and subject). I'm interested in improved handling of aborted
>> > connections (at least most of them). That's my end goal.
>> >
>> > read=-1 solely does not provide sufficient information to be able
>> > to distinguish between malformed request bodies and actual aborted
>> > connections.
>>
>> How is Tomcat supposed to determine the difference?
>>
>> > That's why the ServletInputStream#readLine API says: Returns: an
>> > integer specifying the actual number of bytes read, or -1 if the
>> > end of the stream is reached Throws: IOException - if an input or
>> > output exception has occurred
>>
>> End-of-stream is not an exceptional condition.
>>
>> > I understand that detecting aborted connections is not always
>> > possible because of the missed handshakes but given that apache2
>> > and tomcat are most likely in the same local network and assuming
>> > the protocol closes sockets properly, as long as apache2 detects it
>> > tomcat should also.
>>
>> You are talking about AJP, which does not close connections between
>> the reverse proxy (httpd) and Tomcat. So... what event are you looking
>> for that Tomcat can use to signal an error?
>>
>
> You're spot on for the source of confusion. I thought AJP does close the
> connection between the reverse proxy and tomcat based on the apache log
> below (especially line 3 and 6).
>
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [info]
> ajp_service::jk_ajp_common.c (2773): (directory_service) sending request
> to tomcat failed (unrecoverable), because of client read error (attempt=1)
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [debug]
> ajp_reset_endpoint::jk_ajp_common.c (851): (directory_service) resetting
> endpoint with socket 23 (socket shutdown)
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [debug]
> ajp_abort_endpoint::jk_ajp_common.c (821): (directory_service) aborting
> endpoint with socket 23
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [debug]
> jk_shutdown_socket::jk_connect.c (932): About to shutdown socket 23 [
> 127.0.0.1:42538 -> 127.0.0.1:15443]
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [debug]
> jk_is_input_event::jk_connect.c (1383): timeout during poll on socket 23 [
> 127.0.0.1:42538 -> 127.0.0.1:15443] (timeout=100)
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [debug]
> jk_shutdown_socket::jk_connect.c (1016): Shutdown socket 23 [
> 127.0.0.1:42538 -> 127.0.0.1:15443] and read 0 lingering bytes in 0 sec.
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [debug]
> ajp_done::jk_ajp_common.c (3282): recycling connection pool for worker
> directory_service and socket -1
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [debug]
> jk_handler::mod_jk.c (2921): Consumed 0 bytes of remaining request data
> for worker=directory_service
> [Wed Jan 17 14:42:41 2018] [23791:140542260176640] [info]
> jk_handler::mod_jk.c (2984): Aborting connection for
> worker=directory_service
>
> And also based on the ajp workers documentation which has specific
> recovery_options 4 that closes the connection to tomcat if an error when
> writing back the answer to the client is detected. Yes, this is for write
> not read.
>
> So, the next question is whether there is a way to have connections
> between apache and tomcat closed when aborted.
>
>
>
>> > I therefore think my expectation for an IOException when trying to
>> > read is justified.
>> >
>> > Do you still think otherwise?
>>
>> I do. It's not really up to Tomcat to verify that the client sent all
>> of the data it intended to send.
>>
>>
> George
>

Re: [OT] No movement at Debug mode

2018-01-26 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

All,

On 1/23/18 10:58 AM, Christopher Schultz wrote:
> The MySQL Connector/J simply has a bug. Upgrade to the latest
> version to see if they have fixed it.
> 
> I gave up trying to convince them that it was a problem and that
> they needed to fix it, because I guess they fundamentally don't
> understand what it means to want to be able to "completely
> deregister the driver and shutdown all threads".

I've been reading the release-notes for some of the more resent
versions of MySQL Connector/J, and this[1] looks interesting:

"
... [blaming Tomcat for our problems blah blah]...

The implementation of AbandonedConnectionCleanupThread has now been
improved, so that there are now four ways for developers to deal with
the situation:

* When the default Tomcat configuration is used [...] Connector/J now
detects the stopping of the web application within 5 seconds and kills
AbandonedConnectionCleanupThread

* When Tomcat's context is configured with the attribute
clearReferencesStopThreads="true" [... blah blah Tomcat does stupid
stuff blah blah ...]

* When a ServletContextListener is implemented within each web
application that calls
AbandonedConnectionCleanupThread.checkedShutdown() on context
destruction, Connector/J now, again, skips this operation if the
driver is potentially shared with other applications. No warning about
the thread being unstoppable is issued to Tomcat's error log in this
case.

* When AbandonedConnectionCleanupThread.uncheckedShutdown() is called,
the AbandonedConnectionCleanupThread is closed even if Connector/J is
shared with other applications. However, it may not be possible to
restart the thread afterwards.

"

It would be nice to know (a) how Connector/J determines (in scenario
#3) whether or not Connector/J is being "shared with other
applications". How do they stop Tomcat from logging a warning in this
case?

It would also be nice to know why (in scenario #4) the
AbandonedConnectionCleanupThread cannot be restarted if necessary.
This seems like bad design to me, and a continued failure to
understand what is going on and how developers need to interact with
the libraries they use.

I also don't understand why the thread is *always* launched.
Connector/J claims that "only queries issued with execution-timeouts
cause that thread to be launched" bug I don't have an application that
uses any query-timeouts and that thread is ALWAYS running.

- -chris

[1] https://dev.mysql.com/doc/relnotes/connector-j/5.1/en/news-5-1-41.ht
ml
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlprkbIdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFgjfhAAh+O83mT0ZvfstEzi
IbVqTJIiUVFstmjvtagwBO6wEsdJFRckRrWa3flRM7O/5pX3XPIug5cRof6QaK4R
BCpJGqtunkCGU0faNoqV82Um6MmKwMrhl8ifZBDbsbN2zhqxtRLd/GDIMh27MY3f
e/WrZiXWRzQKDeCqQvOGfVjjGIYYCwrlVOwGCph9uY1+0rLZZilVoP2WAe7mSUQ+
FRMMYsC6YFkwUj0C2EK1ZKi958zfN+Yvk4rg2QlRpB+hwm5JNldHmUgHDubBeUcI
USh7bDa3gqrT2r7zxhwZt4uiNcZ8/odrVcJj+G6156JXXTWm7GgHmgHVDFd/cBSE
Sr4mufZvL9BT0eGD91UldlEybjSi0ikWDt+7lkJgd9y03CEaNrihv+k+ANk1Th8Z
WpuRJlP4emK88bgNSp1ijayqxIxwuDoHGyvUtTfDdkoDCSp95F+fhGATYM7Aiscn
1I1G2KZAdSlKc1c6WK6jPBweyxMPDBMby9WjiCGrVri6aKAAvXHgVtDT/ZbLThga
GzrzSl3OIUgvRjjtcTv7s8Vsv34K/xzYyEUsEbFsNuzKC4CHxaDj/6fxhXraKnTW
uBTyVdhp9vOVgdQLrOFuqbxcyzJ6MtTRWPRKWruPnq+4jsp8SxDk00h/4VW2URhT
Qufn7J7DCl2ZEwvPhPUJx6QYAoE=
=zDYj
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-01-26 Thread Serge Perepel

-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]

>This is likely to get looked at faster if you provide code that other people 
>can run that will reproduce the issue you are seeing rather than expecting 
>someone else to construct the test case for you.

Here is how you can reproduce it:

Server websocket:

package ad.ecs.websocket;

import java.io.IOException;

import javax.websocket.CloseReason;
import javax.websocket.OnClose;
import javax.websocket.OnError;
import javax.websocket.OnMessage;
import javax.websocket.OnOpen;
import javax.websocket.Session;
import javax.websocket.server.ServerEndpoint;

@ServerEndpoint(value = "/asyncMsg")
public class TestWebsocket {
@OnOpen
public void open(Session session) throws IOException{
session.getBasicRemote().sendText("Connection Established");
}

@OnMessage
public String login(String sessionID, Session session) {
//you can do this instead of exception and it will still leak memory
//try {
//session.close(new CloseReason(CloseCodes.GOING_AWAY, "Clearing 
session"));
//} catch (IOException e) {
//e.printStackTrace();
//}
throw new IllegalArgumentException("Testing Leak");
}

@OnClose
public void close(Session session, CloseReason reason) {
}

@OnError
public void error(Session session, Throwable error) {
error.printStackTrace();
}

}

Here is the front end html:








LEAK





Here is js file:

var webSocket = null;

function test() {
console.log("test button clicked");
openSocket();
}

function openSocket() {
console.log("open webSocket");
webSocket = new WebSocket("ws://" + window.location.host + 
"/memoryleak/asyncMsg");

webSocket.onopen = function(event){
console.log("webSocket open");
webSocket.send('test');
};

webSocket.onmessage = function(event){
console.log("webSocket onMessage", event);
};

webSocket.onclose = function(event){
webSocket = null;
console.log("webSocket connection closed", event);
openSocket();
};
}

function closeSocket(){
console.log("close webSocket");
if (webSocket)
webSocket.close();
}

You need to run it on multiple clients if you want it leak fast. We did it with 
8 clients and it leaked 3GB with in like 10 min.

Thank you
[http://www.american-data.com/images/AmericanDataLogoRoundedEmailSignature.png]

Serge Perepel
Software Developer | American Data
p. 608.643.8022 | tf. 800.464.9942 | f. 608.643.2314
se...@american-data.com | www.american-data.com


[Follow us on 
Facebook]   
[Follow us on LinkedIn] 
[Follow us on Twitter]    [Follow us on 
Twitter] 


Notice: This message is the property of 1984 Systems, Inc. (DBA) American Data
and contains information that may be confidential and/or privileged. If you are 
not
the intended recipient, you should not use, disclose or take any action based on
the message. If you have received this transmission in error, please immediately
contact the sender by return e-mail and delete this e-mail,
and any attachments, from any computer.

[ECS 10 Conversion]

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-01-26 Thread Mark Thomas

On 26/01/18 15:11, Serge Perepel wrote:
> When we run our app for 2-3 hours we experience this leak related to our web 
> sockets connections, here is the Memory Analyzer Suspect:
> 
> One instance of "org.apache.coyote.AbstractProtocol$ConnectionHandler" loaded 
> by "java.net.URLClassLoader @ 0x720029098" occupies 2,153,196,128 (88.10%) 
> bytes. The memory is accumulated in one instance of 
> "java.util.concurrent.ConcurrentHashMap$Node[]" loaded by " loader>".

A break down of that ~2Gb would be helpful. How many entries in the Map?
What is the distribution of sizes?

> Keywords
> org.apache.coyote.AbstractProtocol$ConnectionHandler
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.net.URLClassLoader @ 0x720029098
> 
> 
> Also these bugs might be related to this one:
> 
> 
> 
> https://bz.apache.org/bugzilla/show_bug.cgi?id=57546
> 
> https://bz.apache.org/bugzilla/show_bug.cgi?id=57750
> 
> 
> 
> The 57546 bug looks very similar to what we are experiencing. We tested on 
> Linux and so far we do not see the same behavior. Also this is our web socket 
> code:
> 
> 
> 
> package ad.ecs.async.websocket;
> 
> 
> 
> import java.io.IOException;
> 
> import java.util.Arrays;
> 
> 
> 
> import javax.websocket.CloseReason;
> 
> import javax.websocket.OnClose;
> 
> import javax.websocket.OnError;
> 
> import javax.websocket.OnMessage;
> 
> import javax.websocket.OnOpen;
> 
> import javax.websocket.Session;
> 
> import javax.websocket.server.ServerEndpoint;
> 
> 
> 
> import ad.common.Global;
> 
> import ad.ecs.async.AsyncEngine;
> 
> import ad.ecs.async.AsyncResponse;
> 
> import ad.ecs.async.AsyncType;
> 
> import ad.ecs.db.DatabaseEngine;
> 
> import ad.ecs.db.paradox.User;
> 
> import ad.ecs.security.engine.SecurityEngine;
> 
> 
> 
> /**
> 
>  * @author Serge Perepel
> 
>  * @since Aug 23, 2017 12:23:32 PM
> 
>  */
> 
> @ServerEndpoint(value = "/asyncMsg", encoders = AsyncResponseEncoder.class)
> 
> public class ECSAsync {
> 
> 
> 
> @OnOpen
> 
> public void open(Session session) throws IOException{
> 
> session.getBasicRemote().sendText("Connection Established");
> 
> }
> 
> 
> 
> @OnMessage
> 
> public String login(String sessionID, Session session) {
> 
> AsyncEngine.INSTANCE.wsConnect(session, sessionID);
> 
> org.hibernate.Session dbSession = 
> DatabaseEngine.getSessionFactory().openSession();
> 
> try {
> 
>int userID = 
> SecurityEngine.INSTANCE.getUserIDBasedOnSessionID(sessionID);
> 
>User user = (User) dbSession.get(User.class, userID);
> 
>if (user != null) {
> 
>if (user.getNextLogin() == 1) {
> 
>AsyncResponse response = new AsyncResponse();
> 
>response.setType(AsyncType.None);
> 
>response.setData(Arrays.asList("PASSWORD"));
> 
>response.setObjData("PASSWORD");
> 
>
> AsyncEngine.INSTANCE.addTransientResult(sessionID, response);
> 
>}
> 
>}
> 
> } finally {
> 
>dbSession.close();
> 
> }
> 
> return "ok";
> 
> }
> 
> 
> 
> @OnClose
> 
> public void close(Session session, CloseReason reason) {
> 
> AsyncEngine.INSTANCE.wsDisconnect(session);
> 
> }
> 
> 
> 
> @OnError
> 
> public void error(Session session, Throwable error) {
> 
> Global.INSTANCE.getLogHelper().exception(error);
> 
> //session.close(new CloseReason(closeCode, reasonPhrase));
> 
> }
> 
> }
> 
> 
> 
> Front end opens connection and sends invalid sessionID which causes
> 
> the line `AsyncEngine.INSTANCE.wsConnect(session, sessionID);` to throw 
> exception and after that disconnect happens on the front end. At this point 
> front end opens new connection and process goes into the loop. I'm assuming 
> that the connection handler suppose to get freed after a disconnect happen. 
> But it seems to accumulate. You can try this code and just replace code in 
> the login method to always throw the exception. On the front end onDisconnect 
> try to open new connection and send a random message to the web socket.

This is likely to get looked at faster if you provide code that other
people can run that will reproduce the issue you are seeing rather than
expecting someone else to construct the test case for you.

Mark


> 
> 
> 
> Thank you
> 
> Serge
> 
> [http://www.american-data.com/images/AmericanDataLogoRoundedEmailSignature.png]
> 
> Serge Perepel
> Software Developer | American Data
> p. 608.643.8022 | tf. 800.464.9942 | f. 608.643.2314
> se...@american-data.com | 
> www.american-data.com
> 
> 
> [Follow us on 
> Facebook]   
> [Follow us on LinkedIn] 
> [Follow us on Twitter

RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-01-26 Thread Serge Perepel

Forgot to mention that we are running Tomcat 8.5 on Windows 2012 Server

-Original Message-
From: Serge Perepel [mailto:se...@american-data.com] 
Sent: Friday, January 26, 2018 9:12 AM
To: users@tomcat.apache.org
Subject: Suspected memory leak of 
org.apache.coyote.AbstractProtocol$ConnectionHandler object while using 
Websocket

When we run our app for 2-3 hours we experience this leak related to our web 
sockets connections, here is the Memory Analyzer Suspect:

One instance of "org.apache.coyote.AbstractProtocol$ConnectionHandler" loaded 
by "java.net.URLClassLoader @ 0x720029098" occupies 2,153,196,128 (88.10%) 
bytes. The memory is accumulated in one instance of 
"java.util.concurrent.ConcurrentHashMap$Node[]" loaded by "".

Keywords
org.apache.coyote.AbstractProtocol$ConnectionHandler
java.util.concurrent.ConcurrentHashMap$Node[]
java.net.URLClassLoader @ 0x720029098

Also these bugs might be related to this one:

https://bz.apache.org/bugzilla/show_bug.cgi?id=57546

https://bz.apache.org/bugzilla/show_bug.cgi?id=57750

The 57546 bug looks very similar to what we are experiencing. We tested on 
Linux and so far we do not see the same behavior. Also this is our web socket 
code:

package ad.ecs.async.websocket;

import java.io.IOException;

import java.util.Arrays;

import javax.websocket.CloseReason;

import javax.websocket.OnClose;

import javax.websocket.OnError;

import javax.websocket.OnMessage;

import javax.websocket.OnOpen;

import javax.websocket.Session;

import javax.websocket.server.ServerEndpoint;

import ad.common.Global;

import ad.ecs.async.AsyncEngine;

import ad.ecs.async.AsyncResponse;

import ad.ecs.async.AsyncType;

import ad.ecs.db.DatabaseEngine;

import ad.ecs.db.paradox.User;

import ad.ecs.security.engine.SecurityEngine;

/**

 * @author Serge Perepel

 * @since Aug 23, 2017 12:23:32 PM

 */

@ServerEndpoint(value = "/asyncMsg", encoders = AsyncResponseEncoder.class)

public class ECSAsync {

@OnOpen

public void open(Session session) throws IOException{

session.getBasicRemote().sendText("Connection Established");

}

@OnMessage

public String login(String sessionID, Session session) {

AsyncEngine.INSTANCE.wsConnect(session, sessionID);

org.hibernate.Session dbSession = 
DatabaseEngine.getSessionFactory().openSession();

try {

   int userID = 
SecurityEngine.INSTANCE.getUserIDBasedOnSessionID(sessionID);

   User user = (User) dbSession.get(User.class, userID);

   if (user != null) {

   if (user.getNextLogin() == 1) {

   AsyncResponse response = new AsyncResponse();

   response.setType(AsyncType.None);

   response.setData(Arrays.asList("PASSWORD"));

   response.setObjData("PASSWORD");

AsyncEngine.INSTANCE.addTransientResult(sessionID, response);

   }

   }

} finally {

   dbSession.close();

}

return "ok";

}

@OnClose

public void close(Session session, CloseReason reason) {

AsyncEngine.INSTANCE.wsDisconnect(session);

}

@OnError

public void error(Session session, Throwable error) {

Global.INSTANCE.getLogHelper().exception(error);

//session.close(new CloseReason(closeCode, reasonPhrase));

}

}

Front end opens connection and sends invalid sessionID which causes

the line `AsyncEngine.INSTANCE.wsConnect(session, sessionID);` to throw 
exception and after that disconnect happens on the front end. At this point 
front end opens new connection and process goes into the loop. I'm assuming 
that the connection handler suppose to get freed after a disconnect happen. But 
it seems to accumulate. You can try this code and just replace code in the 
login method to always throw the exception. On the front end onDisconnect try 
to open new connection and send a random message to the web socket.

Thank you

Serge

[http://www.american-data.com/images/AmericanDataLogoRoundedEmailSignature.png]

Serge Perepel
Software Developer | American Data
p. 608.643.8022 | tf. 800.464.9942 | f. 608.643.2314 
se...@american-data.com | www.american-data.com

[Follow us on 
Facebook]   
[Follow us on LinkedIn] 
[Follow us on Twitter]    [Follow us on 
Twitter] 

Notice: This message is the property of 1984 Systems, Inc. (DBA) American Data 
and contains information that may be confidential and/or privileged. If you are 
not the intended recipient, you should not use, disclose or take any action 
based on the message. If you have received this tran

Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-01-26 Thread Serge Perepel

When we run our app for 2-3 hours we experience this leak related to our web 
sockets connections, here is the Memory Analyzer Suspect:

One instance of "org.apache.coyote.AbstractProtocol$ConnectionHandler" loaded 
by "java.net.URLClassLoader @ 0x720029098" occupies 2,153,196,128 (88.10%) 
bytes. The memory is accumulated in one instance of 
"java.util.concurrent.ConcurrentHashMap$Node[]" loaded by "".

Keywords
org.apache.coyote.AbstractProtocol$ConnectionHandler
java.util.concurrent.ConcurrentHashMap$Node[]
java.net.URLClassLoader @ 0x720029098


Also these bugs might be related to this one:



https://bz.apache.org/bugzilla/show_bug.cgi?id=57546

https://bz.apache.org/bugzilla/show_bug.cgi?id=57750



The 57546 bug looks very similar to what we are experiencing. We tested on 
Linux and so far we do not see the same behavior. Also this is our web socket 
code:



package ad.ecs.async.websocket;



import java.io.IOException;

import java.util.Arrays;



import javax.websocket.CloseReason;

import javax.websocket.OnClose;

import javax.websocket.OnError;

import javax.websocket.OnMessage;

import javax.websocket.OnOpen;

import javax.websocket.Session;

import javax.websocket.server.ServerEndpoint;



import ad.common.Global;

import ad.ecs.async.AsyncEngine;

import ad.ecs.async.AsyncResponse;

import ad.ecs.async.AsyncType;

import ad.ecs.db.DatabaseEngine;

import ad.ecs.db.paradox.User;

import ad.ecs.security.engine.SecurityEngine;



/**

 * @author Serge Perepel

 * @since Aug 23, 2017 12:23:32 PM

 */

@ServerEndpoint(value = "/asyncMsg", encoders = AsyncResponseEncoder.class)

public class ECSAsync {



@OnOpen

public void open(Session session) throws IOException{

session.getBasicRemote().sendText("Connection Established");

}



@OnMessage

public String login(String sessionID, Session session) {

AsyncEngine.INSTANCE.wsConnect(session, sessionID);

org.hibernate.Session dbSession = 
DatabaseEngine.getSessionFactory().openSession();

try {

   int userID = 
SecurityEngine.INSTANCE.getUserIDBasedOnSessionID(sessionID);

   User user = (User) dbSession.get(User.class, userID);

   if (user != null) {

   if (user.getNextLogin() == 1) {

   AsyncResponse response = new AsyncResponse();

   response.setType(AsyncType.None);

   response.setData(Arrays.asList("PASSWORD"));

   response.setObjData("PASSWORD");

   
AsyncEngine.INSTANCE.addTransientResult(sessionID, response);

   }

   }

} finally {

   dbSession.close();

}

return "ok";

}



@OnClose

public void close(Session session, CloseReason reason) {

AsyncEngine.INSTANCE.wsDisconnect(session);

}



@OnError

public void error(Session session, Throwable error) {

Global.INSTANCE.getLogHelper().exception(error);

//session.close(new CloseReason(closeCode, reasonPhrase));

}

}



Front end opens connection and sends invalid sessionID which causes

the line `AsyncEngine.INSTANCE.wsConnect(session, sessionID);` to throw 
exception and after that disconnect happens on the front end. At this point 
front end opens new connection and process goes into the loop. I'm assuming 
that the connection handler suppose to get freed after a disconnect happen. But 
it seems to accumulate. You can try this code and just replace code in the 
login method to always throw the exception. On the front end onDisconnect try 
to open new connection and send a random message to the web socket.



Thank you

Serge

[http://www.american-data.com/images/AmericanDataLogoRoundedEmailSignature.png]

Serge Perepel
Software Developer | American Data
p. 608.643.8022 | tf. 800.464.9942 | f. 608.643.2314
se...@american-data.com | www.american-data.com


[Follow us on 
Facebook]   
[Follow us on LinkedIn] 
[Follow us on Twitter]    [Follow us on 
Twitter] 


Notice: This message is the property of 1984 Systems, Inc. (DBA) American Data
and contains information that may be confidential and/or privileged. If you are 
not
the intended recipient, you should not use, disclose or take any action based on
the message. If you have received this transmission in error, please immediately
contact the sender by return e-mail and delete this e-mail,
and any attachments, from any computer.

[ECS 10 Conversion]

Re: Tomcat7 with jre 1.7 error during starting

2018-01-26 Thread Rainer Jung


Am 26.01.2018 um 12:08 schrieb Rajesh Cherukuri:

HI

we have a existing  running tomcat version 5 running on solaris with out
any issues ,  recently we have  installed tomcat 7 on the same solaris 10
server  with no application deployed , and configured java version as
jre1.6 in setenv.sh  i couldn't start the tomcats after my installation ,
and below is the error what i get when i start tomcat with java1.7  later i
tired the to configure the java version as 1.8 , i still get the same error
but slightly different error but both are failing at "

*org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:402)*
 can some one let me know if there are any pre-requisites to run a
tomcat on 7 on Soalris  10 ,


there should be no problem running a recent Tomcat 7 with an unchanged 
Oracle HotSpot Java 6, 7 or 8 on Solaris 10. I regularly do this.


Maybe you unpacked a downloaded tarball using Solaris tar? Solaris tar 
has a very specific way of handling long path names and is not 
compatible with gnu tar. Most tarballs noadays are packed using gnu tar 
and should be unpacked with gnu tar as well. Otherwise files can be 
missing or created with a wrong file name.


gnu tar for Solaris should be installed under /usr/sfw/bin/gtar.

Regards,

Rainer


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat7 with jre 1.7 error during starting

2018-01-26 Thread Rajesh Cherukuri

Hi

 here is the full tomcat and JVM versions  tried , and on the lib file name
, i  haven't added anything it is an empty tomcat container that was
unzipped from apache org , and started and there is no application ,custom
jar's that are added


 to my knowledge it is the  "o*rg.apache.catalina.util.ExtensionValidator.*"
that was having issues

Java Version
*java version "1.6.0_91"*
Java(TM) SE Runtime Environment (build 1.6.0_91-b13)
Java HotSpot(TM) Server VM (build 20.91-b07, mixed mode)


*java version "1.8.0_152"*
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)



Tomcat versions

Server version: Apache Tomcat/7.0.62
Server built:   May 7 2015 17:14:55 UTC
Server number:  7.0.62.0
OS Name:SunOS
OS Version: 5.10
Architecture:   sparcv9
JVM Version:1.8.0_152-b16
JVM Vendor: Oracle Corporation

Re: Tomcat7 with jre 1.7 error during starting

2018-01-26 Thread Konstantin Kolinko

2018-01-26 14:08 GMT+03:00 Rajesh Cherukuri :
> HI
>
> we have a existing  running tomcat version 5 running on solaris with out
> any issues ,  recently we have  installed tomcat 7 on the same solaris 10
> server  with no application deployed , and configured java version as
> jre1.6 in setenv.sh  i couldn't start the tomcats after my installation ,
> and below is the error what i get when i start tomcat with java1.7  later i
> tired the to configure the java version as 1.8 , i still get the same error
> but slightly different error but both are failing at "
>
> *org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:402)*
> can some one let me know if there are any pre-requisites to run a
> tomcat on 7 on Soalris  10 ,
>
>
>
>
> *With java 1.6*
>
> ib:/opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/install/:/opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/lib:/opt/CA/CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/sparc:/usr/local/lib:/usr/lib
> 26-Jan-2018 10:49:52 org.apache.catalina.startup.Catalina load
> SEVERE: Catalina.start
> *org.apache.catalina.LifecycleException: Failed to initialize component
> [StandardServer[8075]]*
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:459)
> *Caused by: java.lang.ExceptionInInitializerError*
> at
> org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:806)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> ... 8 more
> *Caused by: java.lang.IllegalArgumentException*
> at
> java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:303)
> at java.util.zip.ZipInputStream.getFileName(ZipInputStream.java:436)
> at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:255)
> at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:82)
> at java.util.jar.JarInputStream.(JarInputStream.java:67)
> at java.util.jar.JarInputStream.(JarInputStream.java:44)
> at
> org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:402)
> at


1. The rules of this mailing list: top-posting is discouraged.
http://tomcat.apache.org/lists.html#tomcat-users
-> 6.

Also ->1. there. You are not saying the exact version number.

2. From the error message text, I think that you have an incorrect jar
file somewhere on your classpath  (in lib/ directory of Tomcat?)

One of differences between JAR files format and plain ZIP format: its
file names are encoded in UTF-8. The ZIP format uses OS locale for
filenames.

If a JAR file was packed with a ZIP tool, the filenames in it might be
broken. The exception apparently tells that a file name is not a valid
UTF-8 string.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat7 with jre 1.7 error during starting

2018-01-26 Thread Rajesh Cherukuri_1

hi 
sorry  i haven’t tried 1.7 , tomcat documentation says 1.6 and above 
> On Jan 26, 2018, at 5:22 PM, Rajesh Cherukuri  wrote:
> 
> its jre7 
> 
> On Fri, Jan 26, 2018 at 11:41 AM, M. Manna  > wrote:
> And did you try running it with jre7? In other words, all 7 ?
> 
> On 26 Jan 2018 18:08, "Rajesh Cherukuri"  > wrote:
> 
> > HI
> >
> > we have a existing  running tomcat version 5 running on solaris with out
> > any issues ,  recently we have  installed tomcat 7 on the same solaris 10
> > server  with no application deployed , and configured java version as
> > jre1.6 in setenv.sh  i couldn't start the tomcats after my installation ,
> > and below is the error what i get when i start tomcat with java1.7  later i
> > tired the to configure the java version as 1.8 , i still get the same error
> > but slightly different error but both are failing at "
> >
> > *org.apache.catalina.util.ExtensionValidator.getManifest(
> > ExtensionValidator.java:402)*
> > can some one let me know if there are any pre-requisites to run a
> > tomcat on 7 on Soalris  10 ,
> >
> >
> >
> >
> > *With java 1.6*
> >
> > ib:/opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/
> > install/:/opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/
> > lib:/opt/CA/CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/
> > sparc:/usr/local/lib:/usr/lib
> > 26-Jan-2018 10:49:52 org.apache.catalina.startup.Catalina load
> > SEVERE: Catalina.start
> > *org.apache.catalina.LifecycleException: Failed to initialize component
> > [StandardServer[8075]]*
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > 39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:459)
> > *Caused by: java.lang.ExceptionInInitializerError*
> > at
> > org.apache.catalina.core.StandardServer.initInternal(
> > StandardServer.java:806)
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > ... 8 more
> > *Caused by: java.lang.IllegalArgumentException*
> > at
> > java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:303)
> > at java.util.zip.ZipInputStream.getFileName(ZipInputStream.
> > java:436)
> > at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:255)
> > at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.
> > java:82)
> > at java.util.jar.JarInputStream.(JarInputStream.java:67)
> > at java.util.jar.JarInputStream.(JarInputStream.java:44)
> > at
> > org.apache.catalina.util.ExtensionValidator.getManifest(
> > ExtensionValidator.java:402)
> > at
> > org.apache.catalina.util.ExtensionValidator.addSystemResource(
> > ExtensionValidator.java:230)
> > at
> > org.apache.catalina.util.ExtensionValidator.addFolderList(
> > ExtensionValidator.java:440)
> > at
> > org.apache.catalina.util.ExtensionValidator.(
> > ExtensionValidator.java:107)
> > ... 10 more
> >
> >
> >
> >
> >
> > *Tomcat configured with Java 1.7 *INFO: The APR based Apache Tomcat Native
> > library which allows optimal performance in production environments was not
> > found on the java.library.path:
> > /lib:/usr/lib:/usr/local/lib:/usr/local/ssl/lib:/usr/share/
> > lib:/usr/sadm/lib:/usr/ccs/lib:/usr/openwin/lib:/usr/dt/
> > lib:/etc/lib:/swhome/retlogic/solve1ultima/SENTINEL_LM/lib:/
> > opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/install/:/
> > opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/lib:/opt/CA/
> > CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/sparcv9:/
> > lib/64:/usr/lib/64
> > Jan 26, 2018 10:46:23 AM org.apache.catalina.startup.Catalina load
> > SEVERE: Catalina.start
> > *org.apache.catalina.LifecycleException: Failed to initialize component
> > [StandardServer[8075]]*
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > 62)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:498)
> >

Re: Tomcat7 with jre 1.7 error during starting

2018-01-26 Thread Rajesh Cherukuri

its jre7

On Fri, Jan 26, 2018 at 11:41 AM, M. Manna  wrote:

> And did you try running it with jre7? In other words, all 7 ?
>
> On 26 Jan 2018 18:08, "Rajesh Cherukuri"  wrote:
>
> > HI
> >
> > we have a existing  running tomcat version 5 running on solaris with out
> > any issues ,  recently we have  installed tomcat 7 on the same solaris 10
> > server  with no application deployed , and configured java version as
> > jre1.6 in setenv.sh  i couldn't start the tomcats after my installation ,
> > and below is the error what i get when i start tomcat with java1.7
> later i
> > tired the to configure the java version as 1.8 , i still get the same
> error
> > but slightly different error but both are failing at "
> >
> > *org.apache.catalina.util.ExtensionValidator.getManifest(
> > ExtensionValidator.java:402)*
> > can some one let me know if there are any pre-requisites to run a
> > tomcat on 7 on Soalris  10 ,
> >
> >
> >
> >
> > *With java 1.6*
> >
> > ib:/opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/
> > install/:/opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/
> > lib:/opt/CA/CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/
> > sparc:/usr/local/lib:/usr/lib
> > 26-Jan-2018 10:49:52 org.apache.catalina.startup.Catalina load
> > SEVERE: Catalina.start
> > *org.apache.catalina.LifecycleException: Failed to initialize component
> > [StandardServer[8075]]*
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:
> > 39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:
> 280)
> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:
> 459)
> > *Caused by: java.lang.ExceptionInInitializerError*
> > at
> > org.apache.catalina.core.StandardServer.initInternal(
> > StandardServer.java:806)
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > ... 8 more
> > *Caused by: java.lang.IllegalArgumentException*
> > at
> > java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:303)
> > at java.util.zip.ZipInputStream.getFileName(ZipInputStream.
> > java:436)
> > at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:255)
> > at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.
> > java:82)
> > at java.util.jar.JarInputStream.(JarInputStream.java:67)
> > at java.util.jar.JarInputStream.(JarInputStream.java:44)
> > at
> > org.apache.catalina.util.ExtensionValidator.getManifest(
> > ExtensionValidator.java:402)
> > at
> > org.apache.catalina.util.ExtensionValidator.addSystemResource(
> > ExtensionValidator.java:230)
> > at
> > org.apache.catalina.util.ExtensionValidator.addFolderList(
> > ExtensionValidator.java:440)
> > at
> > org.apache.catalina.util.ExtensionValidator.(
> > ExtensionValidator.java:107)
> > ... 10 more
> >
> >
> >
> >
> >
> > *Tomcat configured with Java 1.7 *INFO: The APR based Apache Tomcat
> Native
> > library which allows optimal performance in production environments was
> not
> > found on the java.library.path:
> > /lib:/usr/lib:/usr/local/lib:/usr/local/ssl/lib:/usr/share/
> > lib:/usr/sadm/lib:/usr/ccs/lib:/usr/openwin/lib:/usr/dt/
> > lib:/etc/lib:/swhome/retlogic/solve1ultima/SENTINEL_LM/lib:/
> > opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/install/:/
> > opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/lib:/opt/CA/
> > CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/sparcv9:/
> > lib/64:/usr/lib/64
> > Jan 26, 2018 10:46:23 AM org.apache.catalina.startup.Catalina load
> > SEVERE: Catalina.start
> > *org.apache.catalina.LifecycleException: Failed to initialize component
> > [StandardServer[8075]]*
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> > at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:
> > 62)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:498)
> > at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:
> 280)
> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:
> 459)
> > *Caused by: java.lang.Exce

Re: Tomcat7 with jre 1.7 error during starting

2018-01-26 Thread M. Manna

And did you try running it with jre7? In other words, all 7 ?

On 26 Jan 2018 18:08, "Rajesh Cherukuri"  wrote:

> HI
>
> we have a existing  running tomcat version 5 running on solaris with out
> any issues ,  recently we have  installed tomcat 7 on the same solaris 10
> server  with no application deployed , and configured java version as
> jre1.6 in setenv.sh  i couldn't start the tomcats after my installation ,
> and below is the error what i get when i start tomcat with java1.7  later i
> tired the to configure the java version as 1.8 , i still get the same error
> but slightly different error but both are failing at "
>
> *org.apache.catalina.util.ExtensionValidator.getManifest(
> ExtensionValidator.java:402)*
> can some one let me know if there are any pre-requisites to run a
> tomcat on 7 on Soalris  10 ,
>
>
>
>
> *With java 1.6*
>
> ib:/opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/
> install/:/opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/
> lib:/opt/CA/CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/
> sparc:/usr/local/lib:/usr/lib
> 26-Jan-2018 10:49:52 org.apache.catalina.startup.Catalina load
> SEVERE: Catalina.start
> *org.apache.catalina.LifecycleException: Failed to initialize component
> [StandardServer[8075]]*
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:459)
> *Caused by: java.lang.ExceptionInInitializerError*
> at
> org.apache.catalina.core.StandardServer.initInternal(
> StandardServer.java:806)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> ... 8 more
> *Caused by: java.lang.IllegalArgumentException*
> at
> java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:303)
> at java.util.zip.ZipInputStream.getFileName(ZipInputStream.
> java:436)
> at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:255)
> at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.
> java:82)
> at java.util.jar.JarInputStream.(JarInputStream.java:67)
> at java.util.jar.JarInputStream.(JarInputStream.java:44)
> at
> org.apache.catalina.util.ExtensionValidator.getManifest(
> ExtensionValidator.java:402)
> at
> org.apache.catalina.util.ExtensionValidator.addSystemResource(
> ExtensionValidator.java:230)
> at
> org.apache.catalina.util.ExtensionValidator.addFolderList(
> ExtensionValidator.java:440)
> at
> org.apache.catalina.util.ExtensionValidator.(
> ExtensionValidator.java:107)
> ... 10 more
>
>
>
>
>
> *Tomcat configured with Java 1.7 *INFO: The APR based Apache Tomcat Native
> library which allows optimal performance in production environments was not
> found on the java.library.path:
> /lib:/usr/lib:/usr/local/lib:/usr/local/ssl/lib:/usr/share/
> lib:/usr/sadm/lib:/usr/ccs/lib:/usr/openwin/lib:/usr/dt/
> lib:/etc/lib:/swhome/retlogic/solve1ultima/SENTINEL_LM/lib:/
> opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/install/:/
> opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/lib:/opt/CA/
> CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/sparcv9:/
> lib/64:/usr/lib/64
> Jan 26, 2018 10:46:23 AM org.apache.catalina.startup.Catalina load
> SEVERE: Catalina.start
> *org.apache.catalina.LifecycleException: Failed to initialize component
> [StandardServer[8075]]*
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:459)
> *Caused by: java.lang.ExceptionInInitializerError*
> at
> org.apache.catalina.core.StandardServer.initInternal(
> StandardServer.java:806)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> ... 8 more
> *Caused by: java.lang.IllegalArgumentException: MALFORMED*
> at java.u

Tomcat7 with jre 1.7 error during starting

2018-01-26 Thread Rajesh Cherukuri

HI

we have a existing  running tomcat version 5 running on solaris with out
any issues ,  recently we have  installed tomcat 7 on the same solaris 10
server  with no application deployed , and configured java version as
jre1.6 in setenv.sh  i couldn't start the tomcats after my installation ,
and below is the error what i get when i start tomcat with java1.7  later i
tired the to configure the java version as 1.8 , i still get the same error
but slightly different error but both are failing at "

*org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:402)*
can some one let me know if there are any pre-requisites to run a
tomcat on 7 on Soalris  10 ,




*With java 1.6*

ib:/opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/install/:/opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/lib:/opt/CA/CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/sparc:/usr/local/lib:/usr/lib
26-Jan-2018 10:49:52 org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
*org.apache.catalina.LifecycleException: Failed to initialize component
[StandardServer[8075]]*
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:459)
*Caused by: java.lang.ExceptionInInitializerError*
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:806)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 8 more
*Caused by: java.lang.IllegalArgumentException*
at
java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:303)
at java.util.zip.ZipInputStream.getFileName(ZipInputStream.java:436)
at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:255)
at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:82)
at java.util.jar.JarInputStream.(JarInputStream.java:67)
at java.util.jar.JarInputStream.(JarInputStream.java:44)
at
org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:402)
at
org.apache.catalina.util.ExtensionValidator.addSystemResource(ExtensionValidator.java:230)
at
org.apache.catalina.util.ExtensionValidator.addFolderList(ExtensionValidator.java:440)
at
org.apache.catalina.util.ExtensionValidator.(ExtensionValidator.java:107)
... 10 more





*Tomcat configured with Java 1.7 *INFO: The APR based Apache Tomcat Native
library which allows optimal performance in production environments was not
found on the java.library.path:
/lib:/usr/lib:/usr/local/lib:/usr/local/ssl/lib:/usr/share/lib:/usr/sadm/lib:/usr/ccs/lib:/usr/openwin/lib:/usr/dt/lib:/etc/lib:/swhome/retlogic/solve1ultima/SENTINEL_LM/lib:/opt/CA/SharedComponents/lib/:/opt/CA/DSM/scripts/install/:/opt/CA/DSM/caf/lib/:.:/opt/CA/SharedComponents/lib:/opt/CA/CAlib:/opt/CA/DSM/caf/lib:/usr/jdk/packages/lib/sparcv9:/lib/64:/usr/lib/64
Jan 26, 2018 10:46:23 AM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
*org.apache.catalina.LifecycleException: Failed to initialize component
[StandardServer[8075]]*
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:459)
*Caused by: java.lang.ExceptionInInitializerError*
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:806)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 8 more
*Caused by: java.lang.IllegalArgumentException: MALFORMED*
at java.util.zip.ZipCoder.toString(ZipCoder.java:58)
at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:300)
at
java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:122)
at java.util.jar.JarInputStream.(JarInputStream.java:85)
at java.util.jar.JarInputStream.(JarInputStream.java:62)
at
org.apache.cata

Re: AJP Connector not throwing EOFException

Re: [OT] No movement at Debug mode

RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

Re: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

Re: Tomcat7 with jre 1.7 error during starting

Re: Tomcat7 with jre 1.7 error during starting

Re: Tomcat7 with jre 1.7 error during starting

Re: Tomcat7 with jre 1.7 error during starting

Re: Tomcat7 with jre 1.7 error during starting

Re: Tomcat7 with jre 1.7 error during starting

Tomcat7 with jre 1.7 error during starting

13 matches

Site Navigation

Mail list logo

Footer information