Solved Problems - SQL, Java, JBoss

JBoss allocated sequences wrong and were not sync

opiquetus — Wed, 21 Sep 2011 06:43:10 +0000

When i used JBoss 5.1.0 and PostgreSql database and tried to insert / persist a row in database.
Persisted row contained id which was allocated 50 or 250 bigger that sequence which is created for that table and entity.

Suddenly i noticed that entity and sequence were not sync.

Annotation parameter allocationSize and tmp folder remove helped.

@SequenceGenerator(name = “gen_name”, sequenceName = “seq_name”, allocationSize = 1)

Remove:
jboss_5.1.0.GA\server\default\tmp
jboss_5.1.0.GA\server\default\work

eclipse projects disappeared

opiquetus — Mon, 23 May 2011 10:24:22 +0000

http://gobarbra.com/hit/new-7448732dfd1664bc47019b3f819e568f

org.hibernate.ejb.HibernatePersistence cannot be cast to javax.persistence.spi.PersistenceProvider

opiquetus — Mon, 14 Feb 2011 14:25:43 +0000

server\default\deployers\ear-deployer-jboss-beans.xml

true -> false

EARStructureDeployer is already installed.

opiquetus — Mon, 14 Feb 2011 13:32:21 +0000

If you’re using JBoss 6.0.0 in Eclipse Helios: double-click your server, go to the “Deployment” tab, choose “Use the JBoss deploy folder” and check the “Deploy projects as compressed archives”.

OracleXETNSListener system error 1067 has occurred

opiquetus — Thu, 14 Oct 2010 11:40:45 +0000

Problem, this error: System error 1067 has occurred when you’re trying to: net start OracleXETNSListener

Solution:

1. Drink a cup of coffee
2. Make sure you’re not using two separate internet connections e.g. a WLAN + Wired Connection
3. If you are turn off the WLAN or which ever you prefer
4. ????
5. Profit.

Hello World. Goodbye Vagina.

opiquetus — Wed, 30 Jun 2010 09:39:41 +0000

class Hello {
public static void main(String[] args) {
System.out.println(“Hello World. Goodbye Vagina”);
}
}

SVN conflict

opiquetus — Mon, 10 May 2010 06:57:53 +0000

Let’s say you and your colleague are editing a document at the same time. Then the other person saves and commits and there’s a conflict.

Now there are three files in SVN:

OriginalFile.doc
OriginalFile.doc.r20501
OriginalFile.doc.r20502

The last one contains the changes the other person made and committed. What you should do in this situation is:

1. Backup your own copy
2. Revert the file in SVN
3. Update the file in SVN
4. Then you could put locks on for future situations like this
This is done with Tortoise SVN as follows:

a) Select the file
b) Choose ‘Tortoise SVN’
c) ‘Properties’
d) Then click ‘New’ and select ‘svn:needs-lock’
e) Then input “*” without the quotes into the ‘Property Value’ field and press ‘Ok’
5. After the locks make your changes (you have to check them from your backup)
6. Save and commit

Google’s new search design sucks

opiquetus — Fri, 07 May 2010 10:20:03 +0000

Thanks Google for forcing me to change to Altavista again It was fun while it lasted.. the last 10 years. Although I have to say I love the wonder wheel

Required file or directory ‘config/config.xml’ cannot be found.

opiquetus — Mon, 03 May 2010 13:20:14 +0000

Error: Path ‘x:\oracle\Middleware\xxx\domains’ is not a valid WebLogic domain. Required file or directory ‘config/config.xml’ cannot be found.

Solution: Go one step further, either choose the domain you’ve created under this folder or create a new domain.

Web Logic problems with New Server

opiquetus — Mon, 03 May 2010 13:18:15 +0000

Error: The path does not contain a valid WebLogic Server install.
Solution: Your server’s version and eclipse’s version of it do not match. Update your Eclipse if your server is recently downloaded and Eclipse was a package download like this: http://www.oracle.com/technology/software/products/oepe/oepe_11114.html.

So the solution is:

1. Start Eclipse
2. Help – Instal New Software
3. Choose ‘Add’
4. Provide a name (can be anything)
5. Paste this to the URL: http://download.oracle.com/otn_software/oepe/ganymede
6. Install
7. Let Eclipse restart and when adding ‘new server’ it should now work
8. At the time of writing Oracle WebLogic Server 11gR1 Patchset 2 provided the correct location for the files needed here.