Mike London

Claude Moore wrote:Which version of the driver are you using ? Maybe, it's an outdated one, so that autoregistering of the driver doesn't take place. Are you sure you are loading the correct driver class ?
I tried with:

public static void main(String args[]) { try { Driver drv = (Driver) Class.forName("com.mysql.jdbc.Driver").newInstance(); DriverManager.registerDriver(drv); DriverManager.getConnection(URL,"sampleUser", complexPassword); System.out.println(" Connection successfull"); } catch(Exception e) { System.err.println(" Connection failed -> "+e.getMessage()); } }

it worked, bu I also got a warning:

"Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary."

I'm using the new driver.

I'll try creating a separate test class shortly and will report back.

Thanks,

-- mike

Tim Holloway wrote:

Claude Moore wrote:From JDBC 4.0, if I'm not wrong, JDBC drivers are automatically registered when present in classpath;

You are not wrong. There's a special line in the Manifest file in the JDBC driver jar that is detected to register the driver class. Class.forName is extremely obsolete at this point. It's harmless, but unnecessary.

The registerDriver method is supposed to be called by the driver itself when this condition exists, not part of user-written code.

Hi Tim,

I am loading the JDBC driver in the Maven POM.XML.

Yet, without the explicit Class.forName.... I get a unregistered driver exception.

-- mike

Claude Moore wrote:I tried this:

public class TestConnection { private final static String complexPassword = "|\\!&$?^%$"; private final static String URL = "jdbc:mysql://localhost:3306/sample?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC"; public static void main(String args[]) { try { DriverManager.getConnection(URL,"sampleUser", complexPassword); System.out.println(" Connection successfull"); } catch(Exception e) { System.err.println(" Connection failed -> "+e.getMessage()); } } }

And it worked without problems. MySql  Server release is 5.6

That's cool. Thanks.

In any case, I can't get the JDBC logic to work without the Class.forName to explicitly load the driver.

Even with code like below, if I run it, I'll get a "no suitable driver found"

Thanks,

-- mike

Claude Moore wrote:It may silly to ask you this: have you tried using

DriverManager.getConnection(String url, String user, String password)

It should do treat special characters for you.

That's a good idea. I went ahead and instead created a less-powerful user, with no root access, and only SQL access for the database.

Thanks for your reply.

-- mike

Hello,

I have a JDBC MySQL password with lots of special characters, including "%". Now, MySQL works fine using this password from Navicat, WordPress, Drupal, etc., but when I try to connect via a JDBC connection string using this password, I get:

Cannot load connection class because of underlying exception: com.mysql.cj.exceptions.WrongArgumentException: URLDecoder: Incomplete trailing escape (%) pattern

What I've tried:

1. I tried escaping the password in the JDBC connection string like this

final String DATABASE_URL =
               "jdbc:mysql://localhost:3306/lookup?useSSL=false&" +
                       "serverTimezone=America/New_York&user=root&password=\"password_here\"&autoReconnect=true";

2. Different JDBC driver.

3. URLEncoding the password itself. In this case, I get the message that the connection tried three times and gave up -- meaning my URL Encoding wasn't accepted.

---

Would appreciate suggestions how to get around this password issue. I can't change the password itself since there are so many CMS/other clients that actively use the MySQL database.

Thanks very much in advance,

-- mike

Daniel Demesmaecker wrote:Are they on the same host?
This tutorial might help you

Hi Daniel,

Yes, both containers are running on the same Mac.

Thanks,

- mike

I have two docker containers running fine.

1. a Java REST app.
2. MySQL 8

I can access both externally with no problem.

But, when I try to make the Java REST app talk to the MySQL container, I just get a message that after three tries, there was no connection made.

I've tried various ports, host names, docker-created network name, but JDBC just won't connect.

Here's my docker-compose file:
version: '3' services:   app:      build:        context: .        dockerfile: Dockerfile      ports:        - "8089:8080"      volumes:        -  /Users/mike/Library/apache-tomcat-9.0.7/conf/tomcat-users.xml:/usr/local/tomcat/conf/tomcat-users.xml      depends_on:        - db   db:      image: mysql      container_name: test-mysql-docker      ports:           - 3307:3306      volumes:       - ./ZipCodeLookup.sql:/docker-entrypoint-initdb.d/ZipCodeLookup.sql      environment:           MYSQL_ROOT_PASSWORD: "thepass"


Some of the failed JDBC connections include these below (miketest_default is the docker-created network name):

“jdbc:mysql://miketest_default:3306/ZipCodeLookup?useSSL=false&” + “serverTimezone=America/New_York&user=root&password=thepass&autoReconnect=true”; “jdbc:mysql://miketest_default:3307/ZipCodeLookup?useSSL=false&” + “serverTimezone=America/New_York&user=root&password=thepass&autoReconnect=true”; “jdbc:mysql://localhost:3306/ZipCodeLookup?useSSL=false&” + “serverTimezone=America/New_York&user=root&password=thepass&autoReconnect=true”; “jdbc:mysql://localhost:3307/ZipCodeLookup?useSSL=false&” + “serverTimezone=America/New_York&user=root&password=thepass&autoReconnect=true”; “jdbc:mysql://127.0.0.1:33060/ZipCodeLookup?useSSL=false&” + “serverTimezone=America/New_York&user=root&password=thepass&autoReconnect=true”;

----

Any suggestions welcome how to get the Java service in a docker container to be able to reach the MySQL container.

Thanks,

- mike

Hello,

I have a simple testing authentication set up, but it's allowing any user role to access the "hello" class. I'm using an online example as my learning point and the author didn't get it working correctly either...

Here's the override for configure:

 @EnableWebSecurity @Configuration public class SecurityConfiguration extends WebSecurityConfigurerAdapter {    // override configure for user name and password for the controller login    @Override    protected void configure(AuthenticationManagerBuilder auth) throws Exception    {      // Spring 5 tightens up sending password via in-memory methods.      PasswordEncoder encoder = PasswordEncoderFactories.createDelegatingPasswordEncoder();        auth.inMemoryAuthentication()                .withUser("test")                .password(encoder.encode("test"))                .roles("USER")                 .and()                .withUser("demo").password(encoder.encode("demo")).roles("ADMIN");        // add more users and roles here..    @Override    protected void configure(HttpSecurity httpSecurity)    {        try        {            httpSecurity                    .authorizeRequests()                    // allow only USER role for /hello url                    .antMatchers("*/hello/**").hasRole("USER")              //      .antMatchers("**/rest/*")    // if you want to only match some.                     .anyRequest()                    //        .permitAll()                    .fullyAuthenticated()  // make sure they log in using credentials above.                    .and().httpBasic();                        httpSecurity.csrf().disable();        }        catch (Exception e)        {            e.printStackTrace();        }    } }

But the URL using the user = demo (and admin role), still gets to the page: localhost:8088/rest/hello

I've tried various combinations of asterisks with the .antMatchers() method above, but I can't get the security to respect only the user role.

To get the password stuff to work at all, I also had to refactor the online example to use a Password encoder.

Thanks in advance,

-- mike

Ron McLeod wrote:Is the regex [^A-Za-z|[0-9]*] correct? I've never seen a vertical-bar/pipe character in a character class (I'm not a regex expert though).  Why not just define a class simply composed of the three ranges A-Z, a-z, and 0-9 ?

Your code with the expression [^A-Za-z0-9]:Predicate<String> UPPERCASE_WORDS = word -> word.length() > 0 && word.equals(word.toUpperCase()); final String WORD_BOUNDARY = "[^A-Za-z0-9]"; final String TEST_INPUT = "123 SOMEWHERE street"; String result = (Arrays.stream(TEST_INPUT.split(WORD_BOUNDARY)).filter(UPPERCASE_WORDS) .collect(Collectors.joining(" "))); System.out.println(result);
running on Windows 10 with Java 8 produces this result:123 SOMEWHERE

Nice! Thank you.

Yes, your simplified (corrected) RegEx is better. I was confused since it worked fine for me on Java 8 on Mac, but not Java 8 on Windows 7. Same JAR, same Java version. Java 11 worked correctly on both platforms.

Your Regex version fixes it universally. I just wasn't thinking about the Regex being the culprit.

Thanks Ron.

- mike

Problem seems to be the Java 8 version vs. Java 11 Open JDK.

Java 11 gives expected Regex result. Java 8 (even version 191) does not (per the posting above).

Thanks,

- mike

Hello,

I have a simple method in a SparkJava GET method that is supposed to extract only uppercase and numbers from a passed string.

So, "123 SOMEWHERE street" would return: "123 SOMEWHERE".

The code below works as expected (from example above) on the Mac both in Terminal and in Firefox.

Yet, that same code (the JAR file) running on Windows server, does not. The Windows result is "SOMEWHERE". For some reason, the "123" is omitted even though the received URL looks the same as on the Mac. (It's the exact same JAR file).

Here's the code:

get("/extractUpperCase/:passedString", (request, response) ->        { Predicate<String> UPPERCASE_WORDS =                    word -> word.length() > 0 && word.equals(word.toUpperCase());            final String WORD_BOUNDARY = "[^A-Za-z|[0-9]*]";            return (Arrays.stream(request.params("passedString").split(WORD_BOUNDARY))                    .filter(UPPERCASE_WORDS)                    .collect(Collectors.joining(" ")));


WINDOWS SERVER TEST: http://localhost:4567/extractUpperCase/123%20SOMEWHERE%20STREET
RETURNS: SOMEWHERE STREET

----

Mac TEST: http://localhost:4567/extractUpperCase/123%20SOMEWHERE%20STREET
RETURNS: 123 SOMEWHERE STREET

Any ideas why Windows, running the exact same JAR file as the Mac , omits the 123 in the test string?

Windows Server running (java -version): JDK 1.8.0_172
Mac running ($java -version): openJDK 11.

I don't understand how the run time version difference could/should make any difference.

(Baffled.)

Thanks in advance,

- mike

Tim Holloway wrote:

Because, as I said, starting an entire connection pool is even more work than starting a connection from scratch. And if we assume that the point of a micro-service is to be lightweight, that would mean that it's better to be provided with a ready-made source of connections than have to repeatedly create and destroy the whole shebang.

Well, it takes about 20ms to do a basic query with 1,000 records with the current code and I don't see any examples of how to create connections up front but I like your idea at least in principle.

Thanks Tim,

- mike

Tim Holloway wrote:I'm not sure what you're asking. But a Connection Pool is a waste of resources for a single-threaded app. Pools are more suited for multi-threaded and/or multi-user apps where you don't want a given task to hang on to Connections, and you don't want to create a Connection from the ground up every time a task needs one.

My objections to the sample code you pointed to initially were based on the sloppiness of the design and code, not its utility. Both it and the H2 sample are merely trying to show how to set up a Connection Pool and use it. They're illustrative, not real-world uses. In the real world there'd be a lot more going on. And yes, normally you create the pool(s) at or near start-up and would only destroy them at shutdown. Because creating a Connection Pool is at least as much overhead as creating a raw connection, and depending on whether it builds a minimum pool in advance, potentially much more. Pools only pay for themselves when you're asking for Connections multiple times and releasing them in between.

Use-case:
In a micro-service, for example, you have local micro-service method with lifetimes the same as any other method (variables go away at the end of the method). So, on those methods, my question really: "shouldn't you really, instead, create the connection pool instance outside a micro-service (local) method and THEN create connections from that external (persistent) instance from inside the local methods so the connection pool persists?"

Sorry for my lack of clarity. I hope this use-case helps clarify my initial question.

Thanks,

-- mike

Tim Holloway wrote:

Mike London wrote:
Aside from the Class.forName, the code is quite similar to that on the H2 site itself:

http://www.h2database.com/javadoc/org/h2/jdbcx/JdbcConnectionPool.html

Well, yes. It's not exactly rocket science there. The difference is that on the H2 site, they're setting up, running an example, and shutting down. They didn't write code that leaks previous instances of a pool only to create a new pool instance every time you ask for it.

I implemented the connection pool logic in a static method so it's more or less the same.

You never answered my actual question, that I see:  "Does that strategy make sense for a "Connection Pool"? I mean, shouldn't a connection pool be a persistent object future connections call where the Pool manages connections? Or do you look at the Pool from the point of view that in a multi-user environment, multiple users will run the same method and at that point the Connection Pool comes into play?"

Thanks,

Tim Holloway wrote:Your first warning should have been this line:
  Class.forName(DB_DRIVER);
It's probably been 15 years now since that was necessary. This person obviously isn't as clever as he thinks he is.

Secondly, it looks like the getConnectionPool method was attempting to return a singleton object. It obviously fails to do so. And to add insult to injury, it's not even in its own factory class - it's lumped in with the application code.

Moral of story: Not everything you find on the Internet is gold. No matter how high up in a Google search it might appear.

Aside from the Class.forName, the code is quite similar to that on the H2 site itself:

http://www.h2database.com/javadoc/org/h2/jdbcx/JdbcConnectionPool.html